People trying to learn #dddesign along with architectures and architecture patterns, such as #eventdrivenarchitecture, to support its use almost always expect too much from DDD. Almost everyone starts with an unmanageable goal.
If you've set as a goal breaking up a #BigBallOfMud legacy system into a bunch of nice neat little Bounded Contexts by selecting and naming the contexts as an atomic transformation exercise, get ready for pain and suffering. It just doesn't work that way.
1/2
Jenga Smell
- Unknown dependencies and coupling, whether with data, objects, services, and/or architectural mechanisms.
- Changing, disabling, or removing any 1+ may cause unknown and unpredictable failure, even to a catastrophic degree.
#MonolithicArchitecture != Tight Coupling
#BigBallOfMud == Tight Coupling
#ROI is in differentiated strategic innovation, not in a deployable container.
Architect for purpose.
Make Architecture Choices That Free You to Maximize Value and Innovation"The heart of this book is a large set of thinking tools that will help you design a new architecture . . . and the organization needed to support that architecture. The book then offers ways to gradually move from your existing architecture toward the new one. . . .
#SoftwareArchitektur im #Stream
Aufnahme verfügbar!
Big Ball of Mud Architektur des Grauens? Nein, sie hat auch Vorteile
Vaughn Vernon 🟦 🟨 🟧 🟪
Eberhard Wolff