On this episode of the Tech Debt Burndown Podcast, Sarah Wells joins Chris and me to talk about the lessons learned from her decade at the Financial Times, and their journey to implementing microservices.
The same lessons that informed her book, 'Enabling Microservices Success'. We touch on whether the purpose of microservices is to scale a system, or to scale an engineering organization.
By breaking down monoliths into independent domains, teams can reduce cognitive complexity and release software hundreds of times a day.
Sarah warns however that this shift introduces a "maintenance treadmill", requiring robust automation for library upgrades, security patching, and cross-service governance to prevent a sprawl of unmanageable tech debt.







