8 Feb 2016

Domain Service , Application Service and Infrastructure Service

Domain Service :
Encapsulates business logic that doesn't naturally fit within a domain object, and are NOT typical CRUD operations - those would belong to a Repository.

Domain Services along with your Domain Objects is sensible

Application Service :
Used by external consumers to talk to your system (think Web Services). If consumers need access to CRUD operations, they would be exposed here.

Application Services will typically use both Domain Services and Repositories to deal with external requests.

Infrastructure Service:
Used to abstract technical concerns (e.g. MSMQ, email provider, etc)

Domain Driven Design : Theory and Practical Step by Step in MVC .Net


1. What is DDD?

2. Why DDD Approach?

3. Components of DDD.

4.Definition of Components of DDD

4. How to start DDD

5. What are Entities.


6. Difference between Entities and Value Objects.

6. How to Define Entities.

7. Bounded Cotexts(BC)

7. Different scenarios in defining Entities.

8. Ubiquitous Language

9. Structuring Ubiquitous language.

10. Entities.

11. Value Objects

10. Value Object and comparison with Entities.

11. What are Aggregates in DDD

12. Aggregates and Aggregate Root.

13. Repository

14. Domain Service , Application Service and Infrastructure Service

14. Domain Events

15. Anti -Corruption Layers

16. Benefits of DDD.

17. Implementation of DDD in Real-time, Demo.