Domain Driven Design: Domain Service, Application Service [closed]

by

Services come in 3 flavours: Domain Services, Application Services, and Infrastructure Services.

  • Domain Services : Encapsulates
    business logic that doesn’t naturally
    fit within a domain object, and are NOT typical CRUD operations – those would belong to a Repository.
  • Application Services : Used by
    external consumers to talk to your
    system (think Web Services). If consumers need access to CRUD operations, they would be exposed here.
  • Infrastructure Services : Used to
    abstract technical concerns (e.g.
    MSMQ, email provider, etc).

Keeping Domain Services along with your Domain Objects is sensible – they are all focused on domain logic. And yes, you can inject Repositories into your Services.

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

Hope that helps!

More Related Contents:

  1. DDD, Anti Corruption layer, how-to?
  2. Logout: GET or POST?
  3. What’s the difference between “Layers” and “Tiers”?
  4. Component based game engine design [closed]
  5. Why do stacks typically grow downwards?
  6. Should services always return DTOs, or can they also return domain models?
  7. What is N-Tier architecture?
  8. Servicestack – architecture & reusing POCOs for everything
  9. what is a store buffer?
  10. When are you truly forced to use UUID as part of the design?
  11. Should I abstract the validation framework from Domain layer?
  12. On 32-bit CPUs, is an ‘integer’ type more efficient than a ‘short’ type?
  13. What am I not understanding about REST?
  14. Microservices – best practices to retrieve the related data to specific user from the other micro services with the minimal memory/time loss
  15. Best way to store Badge criteria?
  16. How do you organize your small reusable cffunctions?
  17. dma vs interrupt-driven i/o
  18. Difference between a “coroutine” and a “thread”?
  19. How to list supported target architectures in clang?
  20. What is opinionated software?
  21. What is a “feature flag”?
  22. How to detect target architecture using CMake?
  23. CMake Multiarchitecture Compilation
  24. Where should I store photos? File system or the database? [duplicate]
  25. What’s the difference between REST & RESTful
  26. When to Redis? When to MongoDB? [closed]
  27. iOS app submission : missing 64-bit support
  28. Architecture more suitable for web apps than MVC?
  29. Is it ok for entities to access repositories?
  30. DAO and Service layers (JPA/Hibernate + Spring) [duplicate]

Leave a Comment