I'm teaching a two day masterclass at @GOTOcon Copenhagen this September, and it's built around the part of modernization everyone skips. That's why I built it around what I actually saw work while helping organizations through modernization at #AWS, and before that at #DAZN, where we took a monolith and turned it into over 200 hundred microservices spread across tens of teams without losing the plot along the way. The techniques in this workshop are the ones that shortened how long it took to get a proper modernization in place, not the ones that look good on a slide. Most teams reach for a target architecture diagram before they've done the harder work of finding real boundaries, understanding which architectural characteristics should actually drive the modernization goals, and building a team structure that will hold once the new architecture is live rather than fight it. We'll also get into where AI genuinely speeds this work up and where it just adds noise, which matters more right now than most people give it credit for. Over September 28 and 29, working with a small group on a realistic case study, we'll cover evolutionary architecture principles, Event Storming, trade off analysis for architecture decisions, extracting a first service step by step, what platform engineering should centralize versus what teams own, and team topologies for decentralizing decisions while keeping teams aligned. In this 2 days workshop, most of the time is spent applying these techniques in groups and getting feedback. If you're a senior developer, architect, or technical lead working on a system that's outgrown its shape, this one's for you. Details and registration: gotocph.com/2026/masterclass…