Context oriented architecture - Put the boundary in the right place
2 likes1,635 views
The document discusses context-oriented architecture, emphasizing the importance of user and customer contexts within software development. It highlights the need for collaboration among domain experts, developers, and designers, and cautions against unnecessary complexity in design. Additionally, it addresses concerns regarding data integrity, transactional consistency, and architectural decisions in software processes.
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_
- 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.
- 12. Just because you can doesn't mean you should.
- 13. Context Matters
- 14. Model
- 16. User User Context Customer Context - Register - Login - Verification - Store card - Charge card - Apply as customer
- 17. User User Context Customer Context - Register - Login - Verification - Store card - Charge card - Apply as customer Identity
- 18. Behaviours, not only data
- 19. Our architecture
- 21. API Client Domain Model Controller Command Bus Persistence HTTPClient QueueClient Domain Model Controller Command Bus Persistence HTTPClient QueueClient
- 29. Behavioural entities AKA rich modeling
- 32. Unit Testing
- 44. Third party service integration
- 46. Command Handler Model API Client Worker third partyQueue Domain Events Worker third partyQueue Worker third partyQueue
- 52. Pitfalls
- 53. Value Object (Doctrine embeddable)
- 54. 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
- 56. Referential integrity Because each service has his on db, you should find another way to enforce the referential integrity
- 58. Transactional consistency We are violating the transactional consistency because weβre using the UOW to persist both Investor and Loan
- 59. βAt the end of the day we are selling shoes.β @cirpo
- 60. Credits
- 61. Thank you.
- 62. Questions?