Practicing Clean Architecture and Domain Driven Design With ASP.NET Core
•
1 like•107 views
High level introduction to Domain driven design and CQRS based system.
Recommended
More Related Content
Similar to Practicing Clean Architecture and Domain Driven Design With ASP.NET Core
Similar to Practicing Clean Architecture and Domain Driven Design With ASP.NET Core (20)
Recently uploaded
Recently uploaded (20)
Practicing Clean Architecture and Domain Driven Design With ASP.NET Core
- 1. First step towards Microservice
- 2. Ratan Sunder Parai Senior Software Engineer Secure Link Services LTD. (SELISE) contact@ratanparai.com @ratanparai https://www.ratanparai.com
- 3. Do ▪ Enterprise Application ▪ Works great with Agile Don’t ▪ Application with low business logic complexity
- 7. ▪ Anti-pattern ▪ Contrary to the basic idea of object-oriented design; combine data and process together ▪ Just a procedural style design
- 11. - Robert C. Martin
- 13. ▪ Not Entity Framework POCO entity ▪ Encapsulate enterprise wide business rules ▪ Object with methods
- 17. Coordinated transaction Eventual Consistency
- 20. LAWS THAT RULE OVER US Moore’s Law Computing power doubles every 18 months Metcalf’s Law Network becomes more useful the more devices are connected to it Conway’s Law Organizations design the system which copy the organization Brook’s Law Adding more people to a late project makes it later
- 21. - Martin Fowler
Editor's Notes
- AnemicDomainModel The fundamental horror of this anti-pattern is that it's so contrary to the basic idea of object-oriented design; which is to combine data and process together. The anemic domain model is really just a procedural style design, exactly the kind of thing that object bigots like me (and Eric) have been fighting since our early days in Smalltalk. What's worse, many people think that anemic objects are real objects, and thus completely miss the point of what object-oriented design is all about.
- https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html
- Entities encapsulate Enterprise wide business rules. An entity can be an object with methods, or it can be a set of data structures and functions. It doesn’t matter so long as the entities could be used by many different applications in the enterprise. If you don’t have an enterprise, and are just writing a single application, then these entities are the business objects of the application. They encapsulate the most general and high-level rules. They are the least likely to change when something external changes. For example, you would not expect these objects to be affected by a change to page navigation, or security. No operational change to any particular application should affect the entity layer.