concept large system in category istio

This is an excerpt from Manning's book Istio in Action.
An aspect to building our system to be agile and quicker to respond to change is to address the complexities of traditional application architectures and how they devolve over time. In the not too distant past, it was very common to build a large system out of highly coupled, co-located components that ran in a single application server. Moreover, as the feature requests piled up, management would respond by adding more developers to a team. As the team grew, and features were hacked in, the structure of the code and architecture devolved into a "big ball of mud". This made changes to the application even more precarious. Many teams were trying to work on the same code base, typically by long-lived developer branches. Re-integration of these branches were highly unpredictable and usually done under the stress of expiring deadlines. Testing was manual, needed coordination, and took a long time. Deployments of the big ball of mud were stop-the-world, "big-bang", high-risk scenarios.