Your comment mirrors the article. A bunch of projection, written out.
Lots of people do microservices for the wrong reason, with the wrong model. They don't realize this model asks for a lot of initial overhead per process for visibility and early investment into figuring out how these services communicate.
For instance, a service that sets off 3-4 layers of HTTP requests is an indicator of a bad microservice architecture.
A service that uses a shared data bus (e.g. Kafka) but can survive without it however...
That doesn't mean things are regressing. People have always done the wrong things for the wrong reasons.
Lots of people do microservices for the wrong reason, with the wrong model. They don't realize this model asks for a lot of initial overhead per process for visibility and early investment into figuring out how these services communicate.
For instance, a service that sets off 3-4 layers of HTTP requests is an indicator of a bad microservice architecture.
A service that uses a shared data bus (e.g. Kafka) but can survive without it however...
That doesn't mean things are regressing. People have always done the wrong things for the wrong reasons.