When modernizing your legacy systems, be careful not to automatically assume that the language your business and domain experts use is correct and should be reflected in your new architecture.
Their language might be influenced by your legacy systems and not an accurate reflection of the concepts in your domain.
Here is the kind of conversation I've had many times...
1/3
#ddDesign #domainDrivenDesign #softwareArchitecture #architectureModernization #archModernization
Two new chapters of my book Architecture Modernization have just gone live.
- Chapter 15: Architecture Modernization Enabling Teams
- Chapter 16: Strategy and roadmaps
These chapters include industry examples from @joaorosa, Scott Millett and David Gebhardt & Christoph Springer.
https://livebook.manning.com/book/architecture-modernization/chapter-15?origin=mailer
Identifying the need for an architecture modernization enabling team (AMET) · Winding down an AMET when the mission has been achieved · Staffing an AMET with suitable team members · Establishing an enduring architecture operating model
Two new chapters added to my book Architecture Modernization.
- Chapter 12: Loosely coupled software architecture
Contains an excelllent industry example from @__maxs__ showing how to refine domain boundaries combining various techniques
- Chapter 13: Internal developer platforms
Includes an amazing story from Antoine Craske about how building a platform was crucial to the business model turn-around at La Redoute
Remember that modernization is more than just rewriting the old system in new technologies and the latest shiny patterns.
It's an opportunity to modernize the full stack, where stack is everything from the business domain itself up to the user experience.
Nick Tune
Nick Tune 🇺🇦