You're reading from Domain-Driven Refactoring A hands-on DDD guide to transforming monoliths into modular systems and microservices

Product type Paperback

Published in May 2025

Last Updated in May 2025

Publisher Packt

ISBN-13 9781835889107

Length 324 pages

Edition 1st Edition

Concepts

Application Development

Authors (2):

Alessandro Colla

Alberto Acerbis

View More author details

Table of Contents (18) Chapters

Preface

1. Part 1: Why Use Domain-Driven Design to Tackle Complexity? FREE CHAPTER

2. Evolution of Domain-Driven Design

3. Understanding Complexity: Problem and Solution Space

4. Strategic Patterns

5. Tactical Patterns

6. Part 2: Refactoring Legacy Systems

7. Introducing Refactoring Principles

8. Transitioning from Chaos

9. Integrating Events with CQRS

10. Refactoring the Database

11. DDD Patterns for Continuous Integration and Continuous Refactoring

12. Part 3: Moving from Monolith to Microservices

13. When and Why You Should Transition to a Microservices Architecture

14. Dealing with Events and Their Evolution

15. Orchestrating Complexity: Advanced Approaches to Business Processes

16. Other Books You May Enjoy

17. Index

Patterns and techniques for effective DDD refactoring

Refactoring is not just about cleaning up code. In a DDD context, it’s a way to ensure the system evolves alongside the business domain. Splitting bounded contexts is one of the most impactful techniques for aligning technical boundaries with shifting business needs. Effective refactoring in a DDD environment requires structured approaches to managing bounded contexts and refining domain models.

By exploring the patterns and techniques that support this process, you will see that they are the same as already discussed in the earlier chapters of this book. That’s because the fundamentals of DDD also apply beautifully to this aspect of refactoring.

As you know, bounded context is a fundamental DDD concept that encapsulates a consistent domain language and model. Over time, as business needs evolve, these contexts may require splitting, merging, or redefinition. In this subsection, we will cover two techniques...