Successfully reported this slideshow.
Your SlideShare is downloading. ×

Leveraging more then DDD Lite in the startup project

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 26 Ad
Advertisement

More Related Content

Slideshows for you (20)

Advertisement

Similar to Leveraging more then DDD Lite in the startup project (20)

Recently uploaded (20)

Advertisement

Leveraging more then DDD Lite in the startup project

  1. 1. Points to consider • First rapide release • Should it be dirty but fast ? • Fear of overengeeniring / overdesign • Lack of explicit domain • Lack of domain expert
  2. 2. What we’re exactly doing ? Phase 1 • Gather user profiles • Offer configurable visual templates • Share on social networks Phase 2 • Web intelligence matching algo • Feedback collecting • Job offer recommendations
  3. 3. Going down the DDD path… • We want to avoid architecture 2011 effect
  4. 4. What DDD could bring us ? • Staying on the right track
  5. 5. What benefit DDD could bring us ? • Staying on the right track • Explicit behavior • Discovering concepts by challenging constantly what we know about the model • Application features are going to change often over the years (Vaughn Vernon IDDD book) • You don’t understand the domain because it’s new (Vaughn Vernon IDDD book)
  6. 6. Strategic design • Working on the use cases from screens • Making a model • Challenging your assumptions • Starting to define UL • Code / Refactor • Iterate over the points above
  7. 7. CQRS… what ? Idea behind • Separate write from reads Points to consider • Do I need a separate data store for r/w ? • Do I need ES ? • Do I need Event Store ? • Do I need Domain Events ? (more DDD part)
  8. 8. UI
  9. 9. UI
  10. 10. Domain
  11. 11. Infrastructure CommandProc
  12. 12. Validation
  13. 13. Validation Ex: 2
  14. 14. Validation Ex: 3
  15. 15. Domain
  16. 16. Breaking the rule • Rule of thumb : One aggregate state modification per transaction
  17. 17. UI
  18. 18. Infrastructure
  19. 19. Wrap up What I’ve achieved • Decoupling • Maintanibility • Extensibility What bothers me • Mapping (« at boundaries, application are not object oriented » Mark Seemann)
  20. 20. Proof

×