Downloaded 16 times
More Related Content
Domain driven design
- 1. Domain Driven Design Tackling Complexityin The Heart Of Software
- 2. agenda 1- What isDDD? 2- Business Logic Layer Patterns 3- DDD Basics 4- DDD Patterns 5- Related Approaches
- 3.
- 4. WhatısDDD? The term firstdescribed by Eric Evans in his book of the same name(2004). Tackling Complexity Int the Heart Of Software
- 5. WhatısDDD? DDD is anapproach to resolve complex and evolving business requirements.
- 6.
- 7. WhatısDDD? How to TamingComplexity? Collaborate with stakeholders
- 8. WhatısDDD? How to TamingComplexity? Where is behavior ?
- 9. WhatısDDD? Modelling Domain Models dependent ontechnologies
- 10. WhatısDDD? How to TamingComplexity?
- 11. WhatısDDD? Modelling Domain Publish News!= Update News UnPublish News != Remove News
- 12. WhatısDDD? Modelling Domain Isolate businessfrom technologies
- 13. WhatısDDD? How to TamingComplexity? Classic Layered Architecture DDD Architecture Focus on business
- 14. WhatısDDD? Modelling Domain Use richdomain model
- 15.
- 16.
- 17.
- 18.
- 19. BLLPatterns Active Record Model, Persistenceto Db, Business All Together
- 20. BLLPatterns Domain Model Focused onCore Business, Persistence Ignored, Model + Business
- 21.
- 22.
- 23. DDDbasıcs Entities Objects that havea distinct identity
- 24. DDDbasıcs Value Objects An objectthat contains attributes but has no identity
- 25. DDDbasıcs Value Objects An objectthat contains attributes but has no identity
- 26.
- 27.
- 28.
- 29. DDDbasıcs Aggregates and AggregateRoot Cluster of Entities and Value Objects
- 30.
- 31.
- 32. DDDbasıcs Refactoring One of themost important rules in DDD
- 33. DDDbasıcs Anemic Domain Modelvs Rich Domain Model
- 34. DDDbasıcs Anemic Domain Modelvs Rich Domain Model
- 35.
- 36. DDDpatterns When you rememberthat DDD is really just “OO software done right”, it becomes more obvious that strong OO experience will also stand you in good stead when approaching DDD. - Jak Charlton
- 37.
- 38.
- 39.
- 40.
- 41. DDDpatterns CQRS - CommandQuery Responsibility Seperation
- 42. DDDpatterns CQRS - CommandQuery Responsibility Seperation
- 43.
- 44.
- 45.
- 46. Relatedthıngs NoSql Technologies DDD verysuitable for NoSql
- 47.
- 48.
- 49.
- 50. For More Informations... Books 1-Eric Evans - Domain Driven Design 2- Jimmy Nilsson - Applying Domain Driven Design And Patterns 3- Vaugh Vernon - Implementing Domain Driven Design Websites - Thinker 1- Martin Fowler - Blog 2- Greg Young 3- Jimmy Bogard 4- http://dddcommunity.org/ 5- InfoQ 6- Pluralsight
- 51.
- 52.
Editor's Notes
- #6 Uygulamaların ihtiyaçlarının sürekli değişmesinden kaynaklı kompleksleşmesi ve sonunda big ball of mud ‘a dönüşmesi. Radikal, Hürriyet
- #9 Burada haber’i modellemek kısmını söyle.
- #11 Uygulamaya başlarken seçtiğimiz database’e göre modelleri oluşturuyoruz.
- #12 Hürriyet’in yenilenmesi örneğini ver.Sabit duran bir business var ortada.Onun için teknoloji farketmez.
- #13 Hürriyet’in yenilenmesi örneğini ver.Sabit duran bir business var ortada.Onun için teknoloji farketmez.
- #15 Hürriyet’in yenilenmesi örneğini ver.Sabit duran bir business var ortada.Onun için teknoloji farketmez.
- #18 https://learnbycode.wordpress.com/2015/04/12/the-business-logic-layer-transaction-script-pattern/
- #25 Value object should be immutable
- #26 Value object should be immutable
- #34 http://www.slideshare.net/AlexandervanTrijffel/applying-domaindriven-design-to-craft-rich-domain-models
- #35 http://www.slideshare.net/AlexandervanTrijffel/applying-domaindriven-design-to-craft-rich-domain-models
- #49 Bir business işlemi sonucunda birden fazla yere bilgi gönderip farklı işlemlerin yapılmasını isteyebiliriz.Bunu en iyi event driven architecture ile yapabiliriz.