I agree. Microservices have no tooling and a shitload of overhead. After working on such a project I think microservices are an anti-pattern. After a certain point you have to maintain state across service boundaries and all hell breaks loose.

By spitting up your application you basically throw away everything a database gives you as far as ordering and atomicity. And you end up building a giant distributed database yourself.

Stay away from microservices. I've seen people try to make it work multiple times, the overhead for failure scenarios, lack of distributed transactions, and eventual consistency multiply the size of the codebase