1 / 13

Embracing Domain-Driven Design and TDD: Insights from Jimmy Nilsson

Dive into the insightful world of Domain-Driven Design (DDD) and Test-Driven Development (TDD) with expert developer and author Jimmy Nilsson. Known for his work in .NET frameworks and enterprise design, Nilsson emphasizes the importance of understanding programming as a path to clarity and simplicity. His blog and resources serve as a guide for developers looking to reduce accidental complexity while effectively managing data persistence, especially when utilizing Entity Framework (EF). Learn about methodologies like DB-first and Code-first, and explore how good design principles endure beyond fleeting frameworks.

roth-serrano
Download Presentation

Embracing Domain-Driven Design and TDD: Insights from Jimmy Nilsson

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. EF + DDD = true? by Jimmy Nilsson

  2. About Jimmy Nilsson Primarily a developer and architect, but also a trainer and author Blog: JimmyNilsson.com/blog/ Twitter: twitter.com/JimmyNilsson Author of ”Applying Domain-Driven Design and Patterns” and ”.NET Enterprise Design” Co-founder and CEO of factor10

  3. Relational database? O/RM or ”manual”? EF or NHibernate? DDD and TDD! EF 3.5, how to prepare for 4? ?

  4. Relational database? O/RM or ”manual”? EF or NHibernate? DDD and TDD! EF 3.5, how to prepare for 4? :-)

  5. Why TDD? TDD isn’t about testing... ...it’s about programming! To write simpler, clearer and more robust and maintainable code!

  6. Why DDD? Accidental complexity is bad ”Programming is understanding” (Kristen Nygaard) ”DDD == OO done right” Context is king Semantics over technology ...

  7. But also with TDD and DDD we most often need to persist data It’s just not the main focus... Assume that we might use a relational database EF? EF3.5 DB-first (generate metadata and classes) IPoco EF4 DB-first (generate metadata and classes) Model-first (”paint” metadata, generate DB and classes) Code-first (”generate” metadata in runtime, generate DB)

  8. Disclaimer Not a review! No production experience... No analysis...

  9. Domain expert: Lotta Developer: Jimmy Who needs a new app...TimeReport! Our story can begin...

  10. Time report

  11. ”- Show me the code!”

  12. Recommendation Frameworks come and go, good design lasts! So... Focus on DDD and TDD!

  13. References [DDD] Eric Evans: Domain-Driven Design [ADDDP] Jimmy Nilsson: Applying Domain-Driven Design and Patterns

More Related