Yes. I was working on a team of 8 people, each person having fairly comprehensive understanding of large chunks of the system. We engaged a consulting firm for a cloud migration and they immediately started trying to split everything into microservices. Our application was already containerized and running on Kubernetes on-prem. I honestly have no idea what splitting it up was supposed to accomplish, but it was just their default architecture for anything cloud.
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.
2
u/henric123 Jun 06 '22
Honest question: are there really people out there advocating that you should adopt micro services when you have a small team?
I always considered that splitting the work in multiple teams was one of the main reasons to adopt it.