Build on Kubernetes from Day One
stackoverflow.blog
stackoverflow.blog
Frankly, I miss those days.
1. I think you should be able to run any service that you are building locally because faster the inner loop or feedback cycle is, faster you can iterate. So starting out right away on kubernetes prevents you from doing that because you can get stuck with unnecessary chores.
2. The blog makes sense in the context of a large organisation. But if you are a small startup or scale up, have simple RoR, Django, LAMP stack. It is really a lot of unnecessary accidental complexity you have to deal with before solving the real problem. You are better off with docker compose.
I really think people forget how complex it is to manage VMs in any sort of reliable, reproducible fashion. In my opinion, there's a lot more complexity in configuring your process management, SSH, key management, host metrics, log exfiltration, reverse proxy, etc than there is in using a managed Kubernetes offering like EKS or GKE. You end up reinventing a lot of things with VMs to get to a state that these managed Kubernetes services give you out of the box.
This doesn't diminish the complexity of using Kubernetes, but the "simpler alternative" is something like Heroku, not EC2 (to be clear, you didn't advocate for EC2, I'm rebutting the predictable, popular argument).