> Markdown version of [/videos/845-domain-driven-transformation-how-to-bring-back-sustainable-architecture-to-legacy-and-monoliths?t=3](https://www.wearedevelopers.com/videos/845-domain-driven-transformation-how-to-bring-back-sustainable-architecture-to-legacy-and-monoliths?t=3). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Domain-Driven Transformation—How to Bring (Back) Sustainable Architecture to Legacy and Monoliths

Taming a legacy monolith doesn't require a high-risk rewrite. Discover how domain-driven transformation untangles a big ball of mud into a sustainable, deployable architecture.

- **Speakers:** Henning Schwentner
- **Event:** WeAreDevelopers LIVE
- **Published:** January 19, 2024
- **Duration:** 1:01:30
- **URL:** https://www.wearedevelopers.com/videos/845-domain-driven-transformation-how-to-bring-back-sustainable-architecture-to-legacy-and-monoliths

## Summary

Transforming a legacy monolith is much like converting an abandoned port warehouse into a modern concert hall—it requires preserving functional value while radically restructuring the internal architecture to serve new needs. Large, aging codebases inevitably devolve into a scattered "big ball of mud," suffering from anemic domain models and entangled dependencies that cause "whack-a-mole" bugs during routine updates. Controlling this complexity is the primary goal of domain-driven transformation, which relies on a divide-and-conquer strategy to establish strict vertical boundaries rather than relying solely on traditional horizontal layering.

The transformation process must begin by stepping away from existing technical implementations to rediscover core business processes. Collaborative modeling techniques like event storming and domain storytelling allow developers and domain experts to map workflows and identify distinct sub-domains. This conceptual map dictates the desired "to-be" architecture, establishing bounded contexts that guide both module boundaries and team structures. Analyzing the "as-is" source code—often aided by architecture fitness functions and static analysis tools like ArchUnit and SonarGraph—then reveals the structural gaps that must be bridged.

Rather than attempting a high-risk "big bang" rewrite, teams should execute the transition iteratively by establishing an improvement backlog alongside the product backlog, dedicating a fixed share of sprint velocity to structural refactoring. Teams decouple dependencies by gradually duplicating shared identifiers and extracting specialized, context-specific domain models, ensuring that every small change remains fully deployable to production. Ultimately, domain-driven transformation is a marathon that leverages strategic design to continuously realign technical systems and team topologies with evolving business realities.

**Keywords:** domain-driven transformation, legacy monolith modernization, domain-driven design, bounded contexts, collaborative modeling, domain storytelling, event storming, architectural refactoring, anemic domain models, vertical slicing, agile improvement backlog, archunit architecture testing, sonargraph code analysis, cross-functional teams, software complexity management, C4 architecture model, strategic tactical design

## Chapters

1. **Transforming legacy monoliths into modern software systems** (00:03) — Modernizing outdated applications requires converting tangled monolithic structures into useful modern components.
1. **Analyzing a legacy car leasing enterprise application** (05:05) — A legacy case study highlights the limitations of outdated J2EE architecture in modern agile workflows.
1. **Diagnosing structural diseases in legacy software systems** (07:59) — Identifying root causes like the big ball of mud, anemic domain models, and poor team organization informs targeted refactoring strategies.
1. **Tackling essential software complexity with strategic design** (11:06) — Controlling software complexity requires systematically dividing large systems into manageable strategic transformations.
1. **Rediscovering domain knowledge through collaborative modeling techniques** (16:31) — Lightweight collaborative tools like event storming and domain storytelling bridge the gap between business processes and technical implementations.
1. **Drawing architectural boundaries to define target subdomains** (21:08) — Grouping specific actor activities uncovers distinct bounded contexts essential for modeling robust target software architectures.
1. **Aligning horizontal current architecture with vertical goals** (24:49) — Analyzing source code reveals layered horizontal dependencies that must be refactored to support vertical, subdomain-oriented modules.
1. **Planning incremental legacy migrations with improvement backlogs** (33:23) — Balancing user stories with strategic refactoring tasks ensures steady architectural improvements without halting product delivery.
1. **Executing incremental code extractions in legacy codebases** (38:33) — Duplicating minimal structural logic into independent contexts enables safe, viable deployment steps that gradually dissolve the monolith.
1. **Realities of sustaining long-term legacy software transformations** (44:46) — Continuous domain-driven improvement is a lengthy marathon that requires persistent teamwork to achieve sustainable code health.
1. **Tools, team topologies, and tracking architectural transitions** (46:14) — Static analysis plugins, automated testing libraries, and mapped cross-functional team boundaries help enforce ongoing architectural health.

## Related Moments

- [Restructuring the monolith using domain-driven design](https://www.wearedevelopers.com/videos/1206-single-server-global-reach-running-a-worldwide-marketplace-on-bare-metal-in-a-cloud-dominated-world) (from "Single Server, Global Reach: Running a Worldwide Marketplace on Bare Metal in a Cloud-Dominated World")
- [Managing domain duplication and evolving early architectures](https://www.wearedevelopers.com/videos/411-it-s-all-about-the-domain-honey-experiences-from-15-years-of-domain-driven-design) (from "It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design")
- [Modernizing legacy applications through proactive leadership](https://www.wearedevelopers.com/videos/1223-coffee-with-developers-babette-wagner) (from "Coffee with Developers - Babette Wagner")
- [Structuring engineering teams around domain bounded contexts](https://www.wearedevelopers.com/videos/64-shared-mobility-for-everyone) (from "Shared mobility for everyone!")
- [Building long-term Angular architectures with domain-driven design](https://www.wearedevelopers.com/videos/5-sustainable-angular-architectures-with-nx-and-strategic-design) (from "Sustainable Angular Architectures with Nx and Strategic Design")
- [Overview of domain-driven design techniques](https://www.wearedevelopers.com/videos/1571-20-years-of-domain-driven-design-what-i-ve-learned-about-ddd) (from "20 Years of Domain-Driven Design: What I’ve Learned About DDD")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Why Event-Driven Architecture Isn’t About Speed (and When You Actually Need It)](https://www.wearedevelopers.com/magazine/745-why-event-driven-architecture-isn-t-about-speed-and-when-you-actually-need-it)
- [How to Avoid Over-Engineering](https://www.wearedevelopers.com/magazine/546-how-to-avoid-over-engineering)
- [Why You Shouldn’t Build a Microservice Architecture](https://www.wearedevelopers.com/magazine/118-why-you-shouldn-t-build-a-microservice-architecture)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Senior Cloud Software Architect (all genders welcome) for our Intelligent Service Operations Hub](https://www.wearedevelopers.com/jobs/ext/1284556-senior-cloud-software-architect-all-genders-welcome-for-our-intelligent-service-operations-hub) at **Rosenxt Group**
- [Senior Cloud Software Architect (all genders welcome) for our Intelligent Service Operations Hub](https://www.wearedevelopers.com/jobs/ext/1693682-senior-cloud-software-architect-all-genders-welcome-for-our-intelligent-service-operations-hub) at **Rosenxt Group**
- [Senior Cloud Native Solution Architect (all genders welcome) - Kubernetes, CNCF, MlOps](https://www.wearedevelopers.com/jobs/ext/66342-senior-cloud-native-solution-architect-all-genders-welcome-kubernetes-cncf-mlops) at **Rosenxt Group**
- [IT Enterprise Architect (m/w/d)](https://www.wearedevelopers.com/jobs/48321-it-enterprise-architect-m-w-d) at **WALTER GROUP**
- [Senior Cloud Native Solution Architect (all genders welcome) - Kubernetes, CNCF, MlOps](https://www.wearedevelopers.com/jobs/ext/101488-senior-cloud-native-solution-architect-all-genders-welcome-kubernetes-cncf-mlops) at **Rosenxt Group**