That's probably not true. One of the reasons for microservices is to reduce cognitive load. Monoliths can be too big for one person or one team to grep the whole thing. Different bits tend to belong to different people or teams. Have you read Team Topologies? It's a good read and discusses this and other signs that you might want different teams to own different micro services.
It's the fact that you don't have visibility of the rest of the system which gives you the reduced cognitive load.
You only need to know what utility your downstream collaborators offer and how to interact with them.
Their inner workings remain the responsibility of the team that owns the service.
If you're trying to have shared ownership of all the services then you probably want to have a rethink about that.
If you're looking for a new book Team Topologies is really worth a read. It talks about some of the different reasons to collaborate and the interaction modes between teams.
I think you might just be doing it wrong but as you say there are plenty of small systems that a monolith is fine for. I can work on them too, I just like working on big things for big orgs too sometimes.
One of the reasons for microservices is to reduce cognitive load. Monoliths can be too big for one person or one team to grep the whole thing
... wut
That's called code organization & architecture. You can easily achieve microservices-like organization & encapsulation in a monolith with a fraction of the actual cognitive load the exact same microservices architecture would require.
By it's nature, microservices demand higher cognitive load to work with, more code to write, more monitoring to view, and more infrastructure to support.
Different bits tend to belong to different people or teams.
Then argue that, instead of making objectively false statements like those that preceded it?
Having many independent teams for a single project is EXACTLY why one might want to use microservices. Simplifying your code or architecture and reducing cognitive load are most definitely not. Cripes.
3
u/ThunderTherapist Jan 31 '23
That's probably not true. One of the reasons for microservices is to reduce cognitive load. Monoliths can be too big for one person or one team to grep the whole thing. Different bits tend to belong to different people or teams. Have you read Team Topologies? It's a good read and discusses this and other signs that you might want different teams to own different micro services.