Hexagonal architecture - sequence of calls
I'm trying to understand hexagonal architecture along with domain-driven design, but I'm confused with command handlers and command buses. Whether this should belong to the application layer or the domain layer?
Also, I could not find any example class or sequence diagrams. Appreciate if someone could provide a sample sequence diagram which also involves command buses.
I would argue that your command handlers will represent your application's API and, therefore, are part of your application 'layer'. These handlers will orchestrate domain objects and services.
IMHO, the command bus is different. I have implemented an hexagonal architecture using a Command Processor pattern. This was essentially a port, implemented as a .Net interface in the application layer. I initially designed it as a bus but went with 'port' interfaces representing a Command Processor and an Event Publisher as these were more abstract and allowed me to use different styles of adapter, including something like NServiceBus.
- Is MediatR library overused in CQRS examples on the web?
- In DDD(Domain Driven Design), how to persist value objects if they are in separate table with surrogate primary key
- Nestjs Dependency Injection and DDD / Clean Architecture
- Replacing service layer with MediatR - is it worth to do it?
- Best Practices for Managing Unbounded Collections within Domain-Driven Design Aggregates
- Domain Driven Design Application Layer in an ASP.NET application
- Nestjs Event Sourcing - Event Persistence
- DDD - Where should third-party API interfaces should be?
- In DDD(Domain Driven Design), can Repository methods accept Entities or Value Objects that the Aggregate is composed from?
- Prevent exception-based control flow in upper layer of Repository pattern
- Paging in NHibernate
- domain driven design repository
- Using domain driven design entities in an ASP.Net application
- Domain Driven Design Auto Incremented Entity Key
- How to handle paging of sub entities with the repository pattern?
- Is Martin Fowler's POEAA implementation of Unit of Work an anti-pattern?
- If View Model property has value with certain length, replace it with query from database.Do it in Controller, Validation Attribute or somewhere else?
- Is Specification Pattern Pointless?
- DDD Read-Only Repositories returning "value objects"
- DDD driven solution structure
- Using Clean Architecture, am I allowed to Switch Context in Domain Layer ( Use Case )/Or Allowed to use Coroutine Specfic Libraries
- Unsigned number instead of checking invariant in DDD
- Layered architecture, Request and Response DTO, or View Models
- DDD why create interface on domain service?
- Handling Multiple Actors in a Use Case in Clean Architecture and DDD
- Should services always return DTOs, or can they also return domain models?
- DDD Entities making use of Services
- Send, Publish and Request/Response in MassTransit
- CQRS and Domain Driven Design: Anemic data model for Query side
- How to design API endpoint from a DDD perspective