Modelling a complex domain with Domain-Driven Design
Your SlideShare is downloading.
×
Check these out next
Recommended
More Related Content
Slideshows for you (20)
Viewers also liked (20)
Similar to Context oriented architecture - Put the boundary in the right place (20)
Recently uploaded (20)
Context oriented architecture - Put the boundary in the right place
- 1. Context Oriented Architecture Put the boundary in the right place May 13th-14th 2016 — Verona, Italy Leonardo Proietti @_leopro_
- 2. github.com/leopro
- 3. “Any intelligent fool can make things bigger, more complex and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction.” Ernst Friedrich Schumacher
- 4. DDD is a learning path
- 5. DDD is a learning path!
- 6. Take care of your Ubiquitous Language
- 7. You need domain experts ...
- 8. … and right devs, UX, designers.
- 9. Prototype Getfeedback Keep going
- 10. Continuous negotiation
- 11. Just because you can doesn't mean you should.
- 12. Context Matters
- 13. Model
- 14. User Context Customer Context Investor Context Borrower Context
- 15. User User Context Customer Context - Register - Login - Verification - Store card - Charge card - Apply as customer
- 16. User User Context Customer Context - Register - Login - Verification - Store card - Charge card - Apply as customer Identity
- 17. Behaviours, not only data
- 18. Our architecture
- 19. API Client Domain Model Controller Command Bus Persistence HTTPClient QueueClient Domain Model Controller Command Bus Persistence HTTPClient QueueClient
- 20. User Context Customer Context API CALL
- 21. User Context Customer Context
- 22. User Context QUEUE Worker (Node.js) Customer Context
- 23. Behavioural entities AKA rich modeling
- 24. Unit Testing
- 25. Mitigate the locking
- 26. Quick Invest Command Handler Model Worker (Node) API Persistence API Client Invest Command Handler Model Queue
- 27. Third party service integration
- 28. Command Handler Model API Client Worker third partyQueue Domain Events
- 29. Command Handler Model API Client Worker third partyQueue Domain Events Worker third partyQueue Worker third partyQueue
- 30. Functional Testing
- 31. Customer Context Investor Context Request Response
- 32. Customer Context Investor Context Request Response HTTP Client Stub
- 33. Pitfalls
- 34. Value Object (Doctrine embeddable)
- 35. Value Object (Doctrine embeddable) All the fields related to the Address in the user table must be nullable and you have to validate them in the model
- 36. Referential integrity
- 37. Referential integrity Because each service has his on db, you should find another way to enforce the referential integrity
- 38. Transactional consistency
- 39. Transactional consistency We are violating the transactional consistency because we’re using the UOW to persist both Investor and Loan
- 40. “At the end of the day we are selling shoes.” @cirpo
- 41. Credits
- 42. Thank you.
- 43. Questions?
- 44. https://joind. in/talk/47383
