A client has a web application that persists data to a local JSON file. They are migrating the application to Heroku. In order for the application to conform to the Twelve-Factor methodology, what changes should an Architect recommend?
I'm a bit unsure on the best approach here. Should I use a parametric test like a t-test or a non-parametric test like the Wilcoxon rank-sum? I'll need to look at the data distribution first to decide.
Haha, option C is classic 'overcomplicate everything' syndrome. Using multiple dynos to ensure availability of a local JSON file? That's overkill, my dude.
I'm torn between A and D. Persisting data to a database makes sense, but a truly stateless app might be the most Twelve-Factor-y approach. I guess it depends on the specific requirements.
Option A seems like the way to go. Persisting data to a local file isn't really cloud-friendly, and the Twelve-Factor methodology emphasizes using external services for things like data storage.
Margo
5 months agoTarra
5 months agoShawn
5 months agoViva
6 months agoMelissa
6 months agoLonna
6 months agoFrancesco
6 months agoDelila
6 months agoShayne
7 months agoVenita
7 months agoKatheryn
7 months agoBettyann
7 months agoCarry
12 months agoKindra
11 months agoTennie
11 months agoPage
12 months agoCaprice
11 months agoMeghann
11 months agoTom
1 year agoGayla
10 months agoMatilda
11 months agoLino
11 months agoHildegarde
12 months agoKris
1 year agoProvidencia
11 months agoSantos
12 months agoJanae
1 year agoHannah
1 year agoMignon
1 year ago