Common ddd pitfalls
•
3 likes•1,561 views
While DDD is becoming more and more popular, there are quite a few potential misinterpretations and malpractices floating around. These issues are time-consuming, and they induce a lot of frustrations and needless yak-shaving experiences. These pitfalls are plenty, ranging from higher level things (for example a lack of focus on the strategic part) to technical things (for example misinterpretations of the repository pattern), and even the surrounding area (for example errors made when"selling DDD" to your team members). By sharing this experience I hope to reduce the huge amount of time and effort people spend on "doing DDD wrong".
Recommended
More Related Content
Viewers also liked
Viewers also liked (18)
Similar to Common ddd pitfalls
Similar to Common ddd pitfalls (20)
Recently uploaded
Recently uploaded (20)
Common ddd pitfalls
- 1. Common DDD pitfalls @ToJans - 2014
- 4. Strategic
- 11. Strategic Ignoring bounded contexts
- 12. Strategic Ignoring bounded contexts
- 17. Strategic Lack of a domain expert
- 18. Strategic Lack of a domain expert
- 19. Strategic Bounded contexts A lot Little POV Amount Up- / Downstream A lot Little Contracts Dependencies Some things that work * * n = 1
- 20. Tactical
- 21. Tactical
- 22. Tactical DDD for non-core domains
- 23. Tactical DDD for non-core domains
- 28. Tactical In repos, “Tell, don’t ask”
- 29. Tactical In repos, “Tell, don’t ask” … but don’t overdo it
- 30. Infrastructure
- 31. Infrastructure BDUF – what you built
- 32. Infrastructure BDUF – what you need
- 35. Infrastructure Frameworks & Libraries: too generic
- 36. Infrastructure Generic frameworks & Libraries => hacks
- 37. Infrastructure Eventual consistency: do you need it?
- 38. Infrastructure Eventual consistency: do you need it?
- 39. Infrastructure Anything: do you need 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 DDD to your peers & bosses
- 41. Selling it Tough
- 43. Selling it This is a different presentation
- 44. Selling it … but I’ll show you the recap
- 45. And now it’s time for a
- 46. And now it’s time for a
- 47. Recap And now it’s time for a
- 48. Strategic • Don’t ignore bounded contexts • Understand Conway’s Law • Think first, act later • Have domain experts Craft BCs and make them explicit
- 49. Tactical • Only in core domains • Find all ways to model them • Repositories = domain only • Repositories = Tell, don’t ask
- 50. Infrastructure • Don’t build a BDUF • Frameworks <> libraries • Avoid hacks • Aim for simplicity, not ease of building
- 51. Selling it • Don’t force feed • Lead by example • One step at a time
- 52. General
- 53. General
- 54. General
- 55. General
- 56. General
- 57. General
- 59. And now it’s time for
- 60. Questions And now it’s time for
- 63. What was the background seeded by?
- 67. Huge blur was applied