Explore >> Select a destination
|
You are here 
|
nickhayden.com | ||
| | | | |
blog.gougousis.net
|
|
| | | | | ||
| | | | |
blog.arkency.com
|
|
| | | | | ? Domain-Driven Rails e-book: Learn how to handle complex Rails apps and business domains. #GET YOUR COPY NOW | |
| | | | |
vladikk.com
|
|
| | | | | Let's do a little experiment: try to explain the gist of Domain-Driven Design to someone who has no clue about it. This, especially doing it succinctly, is not easy. Heck, I struggle with it myself. Bounded contexts, entities, domain events, value objects, domains, aggregates, repositories... where do you even start? To find the order in the apparent chaos, I want to analyze the DDD methodology from a rather unusual perspective - by applying Domain-Driven Design to Domain-Driven Design itself. After all, this methodology is intended to deal with complex domains, isn't it? | |
| | | | |
without.boats
|
|
| | | |||
