Ayush Kumar, GetYourGuide
Two of our core services had quietly become a distributed monolith: neither could function without the other, core data was duplicated across four systems, and recovering from incidents meant coordinating three teams and waiting for databases to sync. This talk is a practitioner's retrospective on how we got there — and how we got out.
We'll walk through the four telltale signs of a distributed monolith, the five architectural decisions we made to fix it (including replacing async replication with GraphQL resolution and consolidating status flags into a single computed field), and the migration strategy that let us cut over without a big-bang release: six weeks of shadow mode and a staged rollout ladder from 1% to 100% of traffic.
If you've inherited services whose boundaries feel wrong but you're afraid to touch them, this talk is for you.

Ayush Kumar is a Senior Software Engineer at GetYourGuide in Berlin, working in the Inventory group on pricing systems. Over eight years in the industry he has focused on distributed systems and service architecture, most recently leading a cross-functional task force to untangle two of GetYourGuide's most entangled services. He spoke on this work at WeAreDevelopers Berlin earlier in 2026, and this is his SREcon debut.

