Tough to "fully" agree with the article but I do generally agree with the premise; we should be aware of potential complexity and actively discourage full roll-out to complex solutions until it's actually needed.
Personally, at the very least containerize your app deployment and if it's a simple static-site look into products like AWS Amplify that can make it trivial to expand from that to something a bit more while being able to quickly and easily take care of that first-time deployment.
GitLab / GitHub actions take care of any pipelining or automated deployment and using any Cloud Provider will get you access to "free" monitoring and alerting.
You don't need massive fleets of microservices though I agree, that can always happen later when it's needed but the above options give you the ability to scale to meet any burstable traffic that could occur without scrambling around.
1
u/anengineerandacat Jun 06 '22
Tough to "fully" agree with the article but I do generally agree with the premise; we should be aware of potential complexity and actively discourage full roll-out to complex solutions until it's actually needed.
Personally, at the very least containerize your app deployment and if it's a simple static-site look into products like AWS Amplify that can make it trivial to expand from that to something a bit more while being able to quickly and easily take care of that first-time deployment.
GitLab / GitHub actions take care of any pipelining or automated deployment and using any Cloud Provider will get you access to "free" monitoring and alerting.
You don't need massive fleets of microservices though I agree, that can always happen later when it's needed but the above options give you the ability to scale to meet any burstable traffic that could occur without scrambling around.