Some weeks ago I just bumped into this very well-written InfoQ article by Srini Penchikala, about Domain Driven Design (DDD)...I found it very interesting because it's really relevant to what I'm doing at the moment.
The author took inspiration from Eric Evans' book "Domain Driven Design", covering the domain modeling and design aspects mainly from a conceptual and design stand-point. On InfoQ is also available "Domain Driven Design Quickly" , a summary of Evan's book.
These writings discuss the main elements of DDD such as Entity, Value Object, Service etc or they talk about concepts like Ubiquitous Language, Bounded Context and Anti-Corruption Layer.
The objective of this article is to cover the domain modeling and design from a practical stand-point on how one would go about taking a domain model and actually implementing it. We will look at the guidelines, best practices, frameworks and tools that the technical leads and architects can use in the implementation effort.
The article includes a sample loan processing application to demonstrate how design aspects and development best
practices discussed here, can be used in a real-world domain driven development project. The sample application uses
frameworks like Spring, Dozer, Spring Security, JAXB, Arid POJOs and Spring Dynamic Modules in implementing the
loan processing domain model. The example code will be in Java, but it should be fairly easy to understand for most
developers, regardless of language background.
No comments:
Post a Comment