4 ms·
The problem is to define the scope of each service. And it is still possible to create spaghetti out of how the services interact and how coupled they are with
by partycoder 10y ago
The problem is to define the scope of each service. And it is still possible to create spaghetti out of how the services interact and how coupled they are with each other.
If done poorly it is like trading one problem with another problem.
- lgunsch 10y agoYes, I have definitely experienced this. At the company I work at we have dozens of super tiny services that could have been replaced with a single class, or module in a code-base. Each of the dozens of microservices gets it's very own dedicated AWS load balancer, RDS instance, and Auto-Scaling Group in multiple regions. Just the infrastructure management alone is monumental. Edit: punctuation.