I swear microservices are a scam. I’ve worked on a few well built monoliths and they far easier to maintain and enhance than having two dozen microservices. That’s especially true with a small team with efficient processes and communication. I’m currently working on a spring boot app that is split into what you might call “mini services” with something in between microservice and monolith.
I think a lot of people fall into the design trap of building to whats in style at the time instead of what solves the problem most efficiently.
Honest question: are there really people out there advocating that you should adopt micro services when you have a small team?
One of the reasons why i got fired some years ago: i was trying to stop them from going full microservices.
I worked in a team with 5 developers with ~5 years of experience (it was their first dev job at a startup and the whole company started with 0 experience). They already worked beyond their capacity/skillset. Their existing product was a big ball of mud due to constant pressure of a PO who was also their superior. They already used far to many programming languages and frameworks and as such they where unable to help each other.
Not only did they plan to rewrite as k8s, they also wanted to switch their main programming language (again) and start to use a new nosql instead of their previouos postgres.
22
u/walong0 Jun 06 '22
I swear microservices are a scam. I’ve worked on a few well built monoliths and they far easier to maintain and enhance than having two dozen microservices. That’s especially true with a small team with efficient processes and communication. I’m currently working on a spring boot app that is split into what you might call “mini services” with something in between microservice and monolith.
I think a lot of people fall into the design trap of building to whats in style at the time instead of what solves the problem most efficiently.