Development PracticesConference50min
Strangling the dragon: modernizing legacy systems with the Strangler Fig pattern
This talk explores modernizing legacy systems without risky full rewrites. It presents the Strangler Fig pattern for gradual replacement, combined with Domain-Driven Design and the Inverse Conway Manoeuvre, to evolve architecture safely, avoid over-engineering, and align system design with organizational structure for long-term success.
talk.summaryAiDisclaimer
Daniel Raniz Ranelandfactor10
talkDetail.whenAndWhere
Thursday, June 18, 09:00-09:50
Room 3
talks.roomOccupancytalks.noOccupancyInfo
Stuck in a legacy system that needs modernizing? Feel like the best course of action is to throw it in a dumpster, light it on fire and rewrite everything from scratch - maybe even in a different language?
Hold that thought. While it may be tempting to start a rewrite, rewrites of complicated systems rarely succeed for multiple reasons. Chief among them is time and the fact that not everything can stop and wait for the rewrite, but another important contributor is the second system effect, which usually causes rewrites to be over-engineered and bloated in comparison to what they replace
In this talk, I'll share my experiences with the Strangler Fig pattern, a better approach where the original system is gradually replaced by breaking out or rewriting parts into separate systems. I'll also talk about combining this with Domain Driven Design and how to use the new design to execute an Inverse Conway Manoeuvre to ensure you're working with Conway's law and not against it.
Hold that thought. While it may be tempting to start a rewrite, rewrites of complicated systems rarely succeed for multiple reasons. Chief among them is time and the fact that not everything can stop and wait for the rewrite, but another important contributor is the second system effect, which usually causes rewrites to be over-engineered and bloated in comparison to what they replace
In this talk, I'll share my experiences with the Strangler Fig pattern, a better approach where the original system is gradually replaced by breaking out or rewriting parts into separate systems. I'll also talk about combining this with Domain Driven Design and how to use the new design to execute an Inverse Conway Manoeuvre to ensure you're working with Conway's law and not against it.
Daniel Raniz Raneland
Raniz is a programmer, architect, speaker and coach at factor10. He is a problem solver who keeps track of the bigger picture. He is prestigeless, likes to get into new domains, and loves sharing knowledge and ideas. Raniz has worked with system- and software architecture at several companies since 2010 and has been with factor10 since 2021. When not working he's into beer brewing, sourdough bread, 3D printing and triathlons.