> 12Factor Nbr 3 : Store config in ENV variables.
Yep I can do that. In 2 hours I can convert most of my conf in env var. And my next project will go with ENV var from the start.
> 12Factor Nbr 11 : "each running process writes its log, unbuffered, to stdout"
Yep, give me 5 minutes to do that.
When I read 12 factor, and decided to give it a shot, by the end of the week, my app (2 devs full time for 2 years) got nearly everything nailed down and I was able to benefit from it. The last remaining points were harder to implement but I undestood what I needed to do and why.
Most of the advices of the 12factor manifesto can be applied to any programming language/framework/architecture/buisiness and make the deployment/management of the app at least easier.
When I read your manifest, I did not understand most of it. Even your examples do not "talk" to me :
> In your food ordering workflow, instead of writing a payment processing microservice that captures different failure modes, write a payment processing function that processes a payment or fails. The event system should capture the retry or failure event which is processed thereafter. This ensures your business logic is simple and easy to scale.
What event system ? how does it capture the failure mode ? I have an app that is now 4 years old, on which 6 devs are working full time, what can I do today to make it better in a month or two ?
Why are your trying to force me to use GraphQL and make a tech choice for me ? At no point 12factor says use "HTTP REST JSON API" even is a lot of user will go that road, it's their choice and not forced by the maifesto itself.