I think, most people start with a monolith, so they only have one service. If you add features to a monolithic system, that one service will naturally grow in complexity.
The goal with microservices is two-fold.
Get your complexity under control. If you have clearly defined interfaces between two systems its easier to manage each one of them with a dedicated team than when they are intermingled in a big monolith that has implicit interfaces.
Get rid of undifferentiated work. If you can, for example, extract your authentication and let it be done by a SaaS company, you can safe money and time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
thanks, so do you think it is common to see one or two service over iterations/time to grow in complexity?
and it is a mindset and the microservice architecture to extract individual functionality?
I think, most people start with a monolith, so they only have one service. If you add features to a monolithic system, that one service will naturally grow in complexity.
The goal with microservices is two-fold.
Get your complexity under control. If you have clearly defined interfaces between two systems its easier to manage each one of them with a dedicated team than when they are intermingled in a big monolith that has implicit interfaces.
Get rid of undifferentiated work. If you can, for example, extract your authentication and let it be done by a SaaS company, you can safe money and time.