In a multivendor scenario, it could make sense to split a big monolith in say 2 or 3 components, but I have seen dozen of microservices (one of which just managed 3 read-only tables...).
But if your 6-guys team ends up deploying 6+ microservices, you are doomed, in my huble opinion.
We have exactly two microservices atm: one sends emails, one registers users and creates a backend (one backend per customer with us). Should I hire a team just to adhere to your golden rule? I wrote them myself, no support from anyone needed, they are low maintenance.
Do architecture first, have a modular monolith, if you need microservices, use 'em. The rest if this thread is just a waste of time and a bunch of strong opinions.
I just hate this whole thread. Full of weird assumptions. People here don't know enough about the scenarios to hate on either solution. Do what's right for your project and don't listen to the internet. Easy as that.
1 Microservices = 1 Team
In a multivendor scenario, it could make sense to split a big monolith in say 2 or 3 components, but I have seen dozen of microservices (one of which just managed 3 read-only tables...).
But if your 6-guys team ends up deploying 6+ microservices, you are doomed, in my huble opinion.