>The projects I've seen getting to technical bankruptcy have been with no exception monoliths. With microservices you have the ability to take one service and f

>The projects I've seen getting to technical bankruptcy have been with no exception monoliths. With microservices you have the ability to take one service and fix it, reimplement it or replace it if necessary. The worst kind of technical debt is usually about having the service boundary in the wrong place and crappy APIs. With microservices this problem is amplified. It's harder to unpick a service than it is a module. If you've ever tried debugging a problem across a series of microservices as well, you'll wish you hadn't...