I agree with you that it's not a bad thing - I think it's the main benefit of microservices for most larger organizations, the ability for different teams to control their own destiny and not be blocked on each other.
But there's now a whole bunch of new developers out there who are just starting out and read all about these microservices, and think that it's the way to write web backends, and that if you don't do it that way, you just don't know what you're doing. Even if you're a two person team - you must use microservices if you want to scale out in the future apparently. It's just unfortunate the amount of cargo culting going on.
Except it isn't just newbies. Devs with experience look for that holy grail of architecture. They sell it to management by saying the system will be able to change with any new requested feature with minimal effort.
Until it doesn't. And that change will come and it'll make your fancy architecture look like a tin shack instead of a stately manor.
These devs are loud. And management loves loud. Loud is confidence.
But there's now a whole bunch of new developers out there who are just starting out and read all about these microservices, and think that it's the way to write web backends, and that if you don't do it that way, you just don't know what you're doing. Even if you're a two person team - you must use microservices if you want to scale out in the future apparently. It's just unfortunate the amount of cargo culting going on.