1 / 23

Understanding Domain-Driven Design: Key Concepts and Practical Applications

Join Jimmy Nilsson, a developer, trainer, and author, as he explores the essential aspects of Domain-Driven Design (DDD) in this insightful webcast from 2006. He discusses the complexities of building large-scale, long-lived applications, emphasizing the importance of focusing on the core domain to address issues of complexity and maintainability. Nilsson provides examples, including the modeling of orders and customers, and outlines the key components of DDD such as entities, value objects, and repositories. Gain a clearer understanding of how to effectively implement DDD principles in your projects.

weston
Télécharger la présentation

Understanding Domain-Driven Design: Key Concepts and Practical Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Applying Domain-Driven Design Webcast with UML China 2006-08-30 Jimmy Nilsson www.jnsk.se/weblog/

  2. About Jimmy Nilsson • Primarily a developer, but also atrainer and author • Blogs at www.jnsk.se/weblog/ • Author of Applying Domain-Driven Design and Patterns and .NET Enterprise Design

  3. Main Focus of DDD? • The core is the main focus! • Forget distractions!

  4. ?

  5. Reduced complexity Mapping to domain Testability Knowledge- rich design Maintainability Why DDD? Etc, etc... Why DDD?

  6. Problem Description • A complex, large scale and long lived order application will be built • Some very simple examples of requirements: • Order has a customer, customer has orders • Order has one or more lines • Order has a value • Customer has address • ...

  7. Transaction Script [PoEAA]

  8. Table Module [PoEAA]

  9. Domain Model [PoEAA]

  10. Because of the problem description, we choose Domain Model Now we need a Domain Model style...

  11. Entities [DDD]

  12. Value Objects [DDD]

  13. Aggregates [DDD]

  14. Repositories [DDD]

  15. Factories [DDD]

  16. What problems remain? • Infrastructure... • Assumption 1: Relational database • How? • Assumption 2: O/R Mapping • Which? • Assumption 3: For eg NHibernate

  17. NHibernate • Domain Model style: POCO / Persistent Ignorant (PI) • Mapper style: Framework • Start with: Domain Model, Tables, Metadata • API-Focus: Domain Model • Query language: String-based, Query Object-based • Open source, production version • Many databases are supported • Port of Hibernate 2.0.3 • Focus: ”Only” O/R Mapping

  18. Data Mapper [PoEAA] • For example Customer.hbm.xml <class name="Customer" table="Customers"> <id name="Id" access="field"> <unsaved-value= "00000000-0000-0000-000000000000”> <generator class="guid.comb" /> </id> <property name="Name" access="field.camelcase-underscore" />

  19. CRUD – C _session.Reconnect(); try { _session.SaveOrUpdate(customer); _session.Flush(); } finally { _session.Disconnect(); }

  20. CRUD – R (Customer)_session .Load(typeof(Customer), id);

  21. ? Summary...

  22. Any Questions? ? Thanks for listening! www.jnsk.se/weblog/

  23. References • [DDD] Eric Evans; Domain-Driven Design • [PoEAA] Martin Fowler; Patterns of Enterprise Application Architecture • [NHibernate] nhibernate.sourceforge.net • [ADDDP] Jimmy Nilsson; Applying Domain-Driven Design and Patterns

More Related