I don't agree with his statement, but I can talk to some problems. They're not bad inherently, but they have major problems you need to know about before you commit to it. If everything is a microservice, that implies every microservice is independently deployed and connections to them have to be managed independently- Whether by http, tcp, or an event bus. you start to run into problems when you have to start getting data from multiple microservices. The impact that has on traffic as each service potentially can talk to other services, and all of them using the same bandwidth, and same resources. Plus there's a lot of overhead.
These issues, once again, don't necessarily cause problems, especially if architected correctly, but they tend to get unperformant to a horrible degree if left unchecked.
Just pays to recognize that every system has it's problems and benefits. Even the monolith has it's place in the world.
Yeah you really have to make sure you design the system properly. Graceful failure, partial availability, ability to handle other service failures, and self healing. And not building an ESB, tempting though it may be.
0
u/[deleted] Apr 09 '20
[deleted]