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

Problem and solution space

Among the many phrases apocryphally attributed (https://quoteinvestigator.com/2014/05/22/solve/) to Albert Einstein, there is one that goes as follows:

“If I had an hour to save the world, I would spend 55 minutes defining the problem and only 5 minutes finding the solutions.”

We could summarize this statement by saying that the problem space is the set of all the problems that your application should solve, while the solution space is the set of all solutions that address each given problem.

Allen Newell and Herbert Simon in their book Human Problem Solving argue that we, as human beings, tend to be problem solvers. We see this daily in our team while developing software. We tend to seek and try to find a solution as quickly as possible and leave the problem space as quickly too. We are uncomfortable staying in this area, but it is where our client needs to reside; it is the zone that allows us to acquire more information...

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