Sure, you can orchestrate in K8S to spin up the front end, back end, and database instance, but one day someone has to troubleshoot that. That someone being a dev who doesn't work with K8S all the time - good luck.
Sure, you can orchestrate in K8S to spin up the front end, back end, and database instance, but one day someone has to troubleshoot that. That someone being a dev who doesn't work with K8S all the time - good luck.
This is demonstrably untrue and a hilariously bad take.
Docker absolutely simplifies things. Give me a docker-compose file any day over “install X version of Y and Z version of Q”.
Edit: I am actually not arguing just to argue and think about this a lot. A "real world" example is "well, I need to mock out AWS SQS locally and now I have to pull in a fake local queue" or "I need to mock out RabbitMQ locally", etc. The short answer to those things is that you mostly don't - test the endpoint handling queue messages independently / write integration tests for it if you have to. There is no point to having the whole system mocked on your local - SQS/Kafka/whatever will do what it's supposed to do for the most part.
Assuming conservatively that this is 1B/year and 100K users/day, that's still $273/user/day. What are you selling?
Inventory tracking and auditing for Fortune 500 companies in a SaaS before that.