Explore >> Select a destination
|
You are here 
|
surfingcomplexity.blog | ||
| | | | |
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. | |
| | | | |
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 | |
| | | | |
herbertograca.com
|
|
| | | | | Domain-Driven Design was coined by Eric Evans in his fantastic bookDomain-Driven Design: Tackling Complexity in the Heart of Software, published in 2003. Eric Evans book was key in formalisingmany of the software development concepts that today we take for granted. | |
| | | | |
timilearning.com
|
|
| | | Have you ever wondered how data stored in databases actually gets represented on your computer's hard disk? Or why some queries to your database tables benefit from adding indexes on columns? Well, whether you have or not, here's a series of posts that aim to detail my understanding of the journey from inserting a row to a database table, to actually retrieving that row. | ||
