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
3 months agoTarra
3 months agoShawn
4 months agoViva
4 months agoMelissa
4 months agoLonna
4 months agoFrancesco
4 months agoDelila
5 months agoShayne
5 months agoVenita
5 months agoKatheryn
5 months agoBettyann
5 months agoCarry
10 months agoKindra
9 months agoTennie
9 months agoPage
10 months agoCaprice
9 months agoMeghann
9 months agoTom
10 months agoGayla
8 months agoMatilda
9 months agoLino
9 months agoHildegarde
10 months agoKris
10 months agoProvidencia
10 months agoSantos
10 months agoJanae
10 months agoHannah
11 months agoMignon
11 months ago