Download as PDF, PPTX
Uploaded byKacper Gunia
How a large corporation used Domain-Driven Design to replace a loyalty system
The document discusses how a large corporation successfully utilized domain-driven design to replace its loyalty system, emphasizing practical learning and collaboration. Key takeaways include the importance of delivering value, leveraging legacy systems, and using strategic patterns for iterative design. Additionally, it highlights the need to monitor sociotechnical architecture and emphasizes concepts like microservices, event sourcing, and living documentation.
More Related Content
Similar to How a large corporation used Domain-Driven Design to replace a loyalty system
How a large corporation used Domain-Driven Design to replace a loyalty system
- 1. How a largecorporation used Domain-Driven Design to replace a loyalty system
- 2. Kacper Gunia Independent consultant& Trainer DomainCentric.net @ddd_london @cakper
- 3.
- 4.
- 5.
- 6.
- 7.
- 8. Teams distributed across theglobe @cakper
- 9.
- 10.
- 11. So what did welearn? @cakper
- 12. Let people learn andmake mistakes @cakper
- 13. Facilitate learning → Practicedeliberately → Vary the assignments → Give access to resources → Explore solutions, show options → Collaborate, evaluate and conclude @cakper
- 14. Increase throughput and reducework in progress @cakper
- 15. Work with Conway'slaw @cakper
- 16.
- 17. Delivering value iscooler @cakper
- 18. Functional programming is justa tool @cakper
- 19.
- 20.
- 21. Can we deliversoftware? @cakper
- 22.
- 23.
- 24.
- 25.
- 26. C4 Model: SystemContext Diagram1 1 Simon Brown, https://c4model.com/
- 27. Big Picture EventStorming @cakper
- 28.
- 29. Impact Mapping 2 2 GojkoAdzic, https://www.impactmapping.org/
- 30.
- 31. Design Level EventStorming4 4 Alberto Brandolini, Introducing EventStorming
- 32.
- 33. Model Exploration Whirlpool5 5 EricEvans, http://domainlanguage.com/ddd/whirlpool/
- 34. Leverage existing specs andtests @cakper
- 35. Consider both technical andsocial constraints @cakper
- 36. Constantly monitor and evaluateyour choices @cakper
- 37. Consistency is a businessproblem @cakper
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47. (Do not) Roll yourown Event Store @cakper
- 48. Summary → Legacy isa source of requirements, not design → Use strategic patterns to understand the system → Create and evolve tactical design iteratively → Monitor the sociotechnical architectrue @cakper
- 49. Thank you! Training: StrategicDDD & Sociotechnical Architecture NYC 18th - 19th November 2019 @cakper / DomainCentric.net