Four Strategies for Dealing with Legacy Systems
When an elegant new design concept gets injected into an entrenched legacy system, it typically gets compromised to death because the legacy is an immovable object. This tempts teams into ambitious legacy replacement projects that often run aground, or disappoint.
In this talk for the New York DDD meetup in August 2011, Eric Evans describes four strategies for doing DDD in an environment dominated by messy legacy systems while delivering business value quickly, taking into account different levels of capability and commitment to DDD in the organization. |
REST and DDD: Jim Webber at DDDx 2011Jim Webber, co-author of REST in Practice explains how HTTP, ATOM and other Web technologies can provide a platform for rich business applications, including event-driven systems, as an alternative to middleware. |
RESTful SOA or Domain-Driven Design
Vaughn Vernon advocates using DDD’s Context Mapping when integrating services in a RESTful SOA implementation, avoiding one of SOA’s pitfalls: focusing on services rather than the domain. (QCon SF November 2010) |
A Discussion with Allard Buijze on CQRS with the Axon framework The Axon framework is a Java implementation of the Command and Query Responsibility Segregation. |
Domain-Driven Design Using Naked Objects by Dan Haywood
Domain-driven design (DDD) focuses on what matters in enterprise applications: the core business domain. But applying the DDD principles can be easier said than done. Enter Naked Objects: an open-source Java framework that lets you build working applications simply by writing the core domain classes while Naked Objects takes care of the rest of the application infrastructure for you. This book shows how you can rapidly develop and test domain applications, and then deploy to either conventional architectures or onto Naked Objects itself. Get ready to write some of the best business software of your career.Buy the book
|
