Explore >> Select a destination
|
You are here 
|
www.paepper.com | ||
| | | | |
blog.gougousis.net
|
|
| | | | | [AI summary] The text provides an in-depth exploration of Domain-Driven Design (DDD) concepts, including its purpose, key principles, and practical applications. It discusses the importance of understanding the business domain, the role of domain experts, and the use of models to represent complex systems. The text also covers various DDD tactical patterns such as domain events, aggregates, and the importance of maintaining domain invariants. It highlights the challenges and considerations in implementing DDD, including the need to balance technical design with business requirements, and the value of techniques like Event Storming for information gathering and modeling. The text references several notable speakers and resources, including Stefan Tilkov, Dere... | |
| | | | |
softwarepatternsdemystified.wordpress.com
|
|
| | | | | What is a Domain Object? A domain object represents an entity that is of interest to the business as opposed to an entity that matters only to the application and the developer. The business model will usually be the template on which the domain model is constructed. The "Domain Experts" are typically the business analysts... | |
| | | | |
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. | |
| | | | |
pragprog.com
|
|
| | | Use domain-driven design to effectively model your business domain, and implement that model with F#. | ||
