The Good, The Bad and the Domain

The introduction and implementation of DDD company-wide is marked by stumbling blocks and traps. There are successes and failures in the process. What you should pay attention to, what you must not forget. I'll tell you about my experience, the good, the bad and how the domain fits into it.

Transcript

1. The Good The Bad And The Domain
2. About me
3. Lukasz Goworko Lead Developer lukasz.goworko@allmyhomes.com No Facebook, No Twitter, No Instagram
4. Let’s start
5. We are using DDD talking to Dom ain Experts Do not talk to ... IT intern Ubiquitous Language Context m ap Not using events Core Domain? Only IT We know about events
6. The Good
8. Event Storming
10. “If it hurts, do it more often” Martin Fowler
12. Understand the word domain
13. Problem Domain Business Domain Domains in your app / code
14. Create Big Picture and Focus on Core Domain
15. Context maps with reduced dependencies
16. Talk to all Domain Experts
17. “Listen to the language the domain experts use.” Eric Evans
18. Bedrooms + Living Rooms = Rooms
20. The Bad
21. Object first => how to store
22. Create anemic objects
23. Create your domains around this objects
25. More Dependencies Team => Code
27. Distributed State of Truth
28. linearizability in distributed systems
29. at the end you will have
31. Reichenberger Straße 36 • 10999 Berlin info@allmyhomes.com • +49 30 644 346 97 Geschäftsführer • Dr. Martin Enderle, Florian Frey, Lutz Grimm Handelsregister • Amtsgericht Charlottenburg HRB 166008B Umsatzsteuer-ID (VAT) • DE300352313