Explore >> Select a destination
|
You are here 
|
kenan7.com | ||
| | | | |
www.paepper.com
|
|
| | | | | Domain Driven Design (DDD) is an influential book by Eric Evans from 2004 - sometimes also referred to as "the big blue book". This blog post summarizes some of my own understanding of the book and gives you an introduction to domain driven design. Important definitions Domain The domain is the area in the real world which we are writing a computer program about. Model The model is our representation of our domain. | |
| | | | |
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? | |
| | | | |
blog.bencope.land
|
|
| | | | | There are a number of ways one might approach designing the logic of a domain problem. Most enterprise software engineers may be accustomed to modeling the problem using object-oriented programming, where classes encapsulate behavior and data. In this approach, the design often reflects the use of various design patterns, such | |
| | | | |
rachelcarmena.github.io
|
|
| | | Some characteristics of functional programming | ||
