Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Domain-Driven Refactoring

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

Arrow left icon
Product type Paperback
Published in May 2025
Publisher Packt
ISBN-13 9781835889107
Length 324 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
Alessandro Colla Alessandro Colla
Author Profile Icon Alessandro Colla
Alessandro Colla
Alberto Acerbis Alberto Acerbis
Author Profile Icon Alberto Acerbis
Alberto Acerbis
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: Why Use Domain-Driven Design to Tackle Complexity?
2. Evolution of Domain-Driven Design FREE CHAPTER 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

Dividing the domain into meaningful boundaries

The most obvious advantage of having a ubiquitous language is the ability to easily identify the boundaries around a business problem and split the domain into many subdomains. A business domain is the main area of activity of a company. In the example we will use in this book, the business domain is brewery management. The service that our hypothetical company provides is the production and selling of the best beer in the world! Easy.

It is important to understand that the business domain is not a software application. The software provides the solution you create to help your customer manage their business. A business domain is generally big and complex. So, as you have already discovered, having just one model to describe the whole business is impossible, and it is probably the situation that you will find yourself in when approaching refactoring. You can see the problem of having a “one-size-fits-all” model. It is...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime