Domain-driven design (DDD) is a software development approach that centers around modeling a domain into objects based on how an expert in that domain would naturally describe it. The presentation introduces key DDD concepts like ubiquitous language, context, domain models using entities, value objects, repositories, services, and commands. It notes pros of DDD like separated business rules, readable code, and ease of maintenance, as well as cons like code overhead and a steep learning curve. The presentation concludes by thanking the audience.

1. Introduction to DDD
ThinkApps Live
August 14, 2015
Software House

2. Radosław Mejer
Software House
_radmen
radoslaw.mejer
radmen

3. What is DDD?

5. Concepts of DDD

6. Ubiquitous Language
(naming matters!)

7. Context
(it matters!)

8. Domain
(knowledge base)

9. Model
(abstractions)

10. Building blocks

11. Entity
(object with an identity)

12. Factory
(creates things)

13. Value object
(immutable representation of value)

14. Repository
(talks with DB)

15. Service
(a place where things happen)

16. Service example

17. Command

18. Handler

19. Controller

20. There’s more of it!

21. Pros
● separated layer for business rules
● heavy use of OOP patterns
● separation of concerns
● readable code
● codebase is “live documentation”
● easy to maintain
● clean code!

23. Cons
● code overhead
● steep learning curve
● heavy use of OOP patterns
● requires to change habits
● things need to be named :)

24. There are only two hard things in Computer
Science: cache invalidation and naming things.
̶̶̶̶̶̶̶̶ -- Phil Karlton

25. How DeSmart started to use DDD?

26. Thank you!