On which layer is the data warehousing interface placed in the hexagonal architecture?
As shown in the figure, following the hexagonal architecture pattern, the storage interface seems to be placed in the application layer. But according to the DDD specification, the data storage interface should belong to the domain layer. So what is to be done?
I agree with @Tseng in general. Note that the repository interface is a domain language-specific concept (it's in the ubiquitous language and domain experts must understand the meaning of each repository name and method). So it means it's a port that the domain layer exposes.
Can we use it in the presentation layer? Yes, but it's not recommended. We design an application layer to address some concerns (like opening db connections, starting and committing transactions, etc) that can be reused on many presentation layer methods (separation of concerns). The application layer exposes use case scenarios. The presentation layer initiates the application layer use cases.
In this picture, there are two kinds of repositories. One for the write model (commands that use the domain model) and another for the read model (queries that use another model named read model instead of the domain model to optimize queries).
So this sentence from @Tseng's answer is not quite right:
What "Queries can bypass domain layer" means, is that you don't have to use domain or application services to access the repository
It means that queries (in the CQS/CQRS pattern) use the read model instead of the domain model. We don't use the domain repository in queries. So "bypassing the domain layer" means using another model for queries instead of the domain model.
- What is the difference between maximum number of thread per block vs cuda cores in one SM
- System design: Strategies for dealing with heavy writes to a DB
- laravel/vue design: different ways to handle a loader on a SPA while laravel is processing a job
- How to make multiple sequence diagrams in single page
- Separate build for each architecture but the resulting APK files are identical?
- Buzz words in architecture document
- Is it bad practice to have a constructor function return a Promise?
- Where to place events in a Spring Modulith application?
- Macro definition to determine big endian or little endian machine?
- How exactly does the Spring BeanPostProcessor work?
- Building a suspending resource pool using Kotlin Coroutines
- Since IPv6 is going to replace IPv4, should I develop my new application to support it?
- How to ignore classes in test class with ArchUnit
- Difference between "compute capability" "cuda architecture" clarification for using Tensorflow v2.3.0
- What's the difference between REST & RESTful
- Software design for simultaneously running python programs
- Visitor Design Pattern - return type
- Adding On-Premise node to EKS - Kubernetes
- What's the right ZeroMQ architecture for my scenario?
- Data duplication or async on-demand oriented communication on microservices
- Project / dll architecture to avoid circular references but maintain modularity
- Bluespec Verilog - polymorphic vector type
- Web Application Architecture?
- Service oriented architecture vs Microservices
- What is multi tenancy and ways to achive it?
- Flutter BLoC library: Where to keep the TextEditingController object: in State, in BLoC / Cubit class or in the widget?
- Conflicting REST urls
- Azure pipelines - system.debug variable overriden
- Kafka Streams state store vs MongoDB for state management
- Resources for learning how to design a multi-process software and how to decide which approach to use