Explore >> Select a destination
|
You are here 
|
kenan7.com | ||
| | | | |
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? | |
| | | | |
pragprog.com
|
|
| | | | | Use domain-driven design to effectively model your business domain, and implement that model with F#. | |
| | | | |
blog.thesoftwarementor.com
|
|
| | | | | ||
| | | | |
www.dotnet-tv.com
|
|
| | | [AI summary] The post discusses the Nemerle programming language, highlighting its features and capabilities as a .NET platform language. | ||
