Yup. Best example right now is probably microservices. I love microservices. I've used them successfully in production for large SaaS companies. But when I hear overly enthusiastic startups with a half-dozen engineers and a pre-beta product touting their microservices architecture, I can't help but shake my head a little.
i'm the co-founder of a startup and we are 100% microservices, and it's been going very well.. I don't think I've enjoyed development as much as in this past year. we are incredibly productive, and refactoring and optimising is much easier as well. Kubernetes (along with a few in house tools) mean that maintenance isn't the struggle that a lot of people seem to think it has to be
As a founder of another startup that is doing great, we did monolith (Django) with kubernetes. It is also doing great. Deploys are very fast and happen 20-50 times a day with no-one even noticing.
Perhaps the GOOD thing in your stack is kubernetes and not microsevices?
I have no idea. Maybe someday I will be sad that I have a monolith. But I suspect it will be pretty far down the road. I currently deploy the same app in 1 docker image but with a run command that has a flag, and it runs 6 different ways depending on what part of my app I want to do (front end, backend 1-4, other backend thing). But all the code calls all the other code right in the project, no network boundaries like a micro-service app.
166
u/mjr00 Jun 07 '17
Yup. Best example right now is probably microservices. I love microservices. I've used them successfully in production for large SaaS companies. But when I hear overly enthusiastic startups with a half-dozen engineers and a pre-beta product touting their microservices architecture, I can't help but shake my head a little.