Downloaded 23 times
Uploaded byTom Janssens
Common ddd pitfalls
The document discusses common pitfalls in Domain-Driven Design (DDD) and provides strategic and tactical recommendations for overcoming these challenges. Key points include the importance of understanding bounded contexts, avoiding the build/duplication of frameworks, and the need for domain experts in the process. Additionally, it stresses the significance of a thoughtful approach to modeling core domains.
More Related Content
Similar to Common ddd pitfalls
Common ddd pitfalls
- 1.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11. Strategic Ignoring boundedcontexts
- 12. Strategic Ignoring boundedcontexts
- 13.
- 14.
- 15.
- 16.
- 17. Strategic Lack ofa domain expert
- 18. Strategic Lack ofa domain expert
- 19. Strategic Bounded contextsA lot Little POV Amount Up- / Downstream A lot Little Contracts Dependencies Some things that work * * n = 1
- 20.
- 21.
- 22. Tactical DDD for non-coredomains
- 23. Tactical DDD for non-coredomains
- 24.
- 25.
- 26.
- 27.
- 28. Tactical In repos, “Tell,don’t ask”
- 29. Tactical In repos, “Tell,don’t ask” … but don’t overdo it
- 30.
- 31. Infrastructure BDUF – whatyou built
- 32. Infrastructure BDUF – whatyou need
- 33.
- 34.
- 35. Infrastructure Frameworks & Libraries:too generic
- 36. Infrastructure Generic frameworks &Libraries => hacks
- 37. Infrastructure Eventual consistency: doyou need it?
- 38. Infrastructure Eventual consistency: doyou need it?
- 39. Infrastructure Anything: do youneed it? ”Il semble que la perfection soit atteinte non quand il n'y a plus rien à ajouter, mais quand il n'y a plus rien à retrancher.” Antoine de Saint-Exupéry
- 40. Selling it Selling DDDto your peers & bosses
- 41.
- 42.
- 43. Selling it This isa different presentation
- 44. Selling it … butI’ll show you the recap
- 45. And now it’stime for a
- 46. And now it’stime for a
- 47. Recap And now it’stime for a
- 48. Strategic • Don’t ignorebounded contexts • Understand Conway’s Law • Think first, act later • Have domain experts Craft BCs and make them explicit
- 49. Tactical • Only incore domains • Find all ways to model them • Repositories = domain only • Repositories = Tell, don’t ask
- 50. Infrastructure • Don’t builda BDUF • Frameworks <> libraries • Avoid hacks • Aim for simplicity, not ease of building
- 51. Selling it • Don’tforce feed • Lead by example • One step at a time
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59. And now it’stime for
- 60. Questions And now it’stime for
- 63. What was thebackground seeded by?
- 64.
- 65.
- 66.
- 67. Huge blur wasapplied