Re:Goodbye Microservices: From 100s of problem children to 1...
by thinkmassive on Tuesday July 10, 2018 @01:51PM
(#17500525)
In this case it sounds like they started with a microservice architecture, but CI/CD automation necessary for robust testing and auto-scaling was not in place. The problem of queues getting backed up might have been addressed by adding a circuit breaker, but instead they chose to introduce shared libraries (again, without necessary testing and deployment), which resulted in very tight coupling of the so-called microservices.
[ Parent
| on HN ]
There are no comments on this comment yet.