If you have the feeling something in your application always goes hand in hand, you can group it in a microservice. Sometimes this is obvious, like with authentication or monitoring, but sometimes your application grows through iterations, and one day you see something worth extracting.
Sure, that doesn't help too much when you want to start your application as microservices.
You could try mapping it before you start; sometimes, this gives at least an idea bout the stuff you could outsource.
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.
I would group them logically.
If you have the feeling something in your application always goes hand in hand, you can group it in a microservice. Sometimes this is obvious, like with authentication or monitoring, but sometimes your application grows through iterations, and one day you see something worth extracting.
Sure, that doesn't help too much when you want to start your application as microservices.
You could try mapping it before you start; sometimes, this gives at least an idea bout the stuff you could outsource.
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.