I am rebuilding a software in accounting. This sofware can handle many types of transactions, e.g. sales, inventory restock, and expenses. I have no background
In my organization we're trying to design our microservices based on the Bounded Context (BC) pattern (part of Domain-driven design). While we're doing this we
We are currently using domain driven desing with commands and events. I can not decide in which layer of DDD should event handlers and command handlers resides.
I'm practicing event-storming, with sticky notes and stuffs. But one thing is missing: command validation (rules to be satisfied for a command to be accepted /
Let's assume a monolithic web service. The architectural design is based on the DDD and divides the domain into sub-domains. These are structured according to t
i have this ValueObject : public class Access : ValueObject<Access> { public string ControllName { get; set; } public string ActionName { get;
If someone tries to implement the CQRS pattern without repository in DDD, in which layer should it be done? Infrastructure or Application Layer?
Hi everyone, I'm a little bit lost with a problem thinking in ddd way. Imagine you have an application to sell concert ticket. So you have an entity which is ca
Let's consider that we use OOP. Is a Subdomain a class? And Bounded Context is a set of classes that are used together for the only purpose(ideally)? Can on sub
Leaders in DDD cite the Application Layer as the appropriate place for Transaction Management. For example, from Vince Vaughn: Application Services reside in t
In my limited experience, I've been told repeatedly that you should not pass around entities to the front end or via rest, but instead to use a DTO. Doesn't Sp
My Aggregate is like this: public class Order : AggregateRoot { private readonly List<OrderItem> _items = new(); public DateTime Date { get; set;
Config\Services is a class made to reduce huge code development on singleton. Unfortunately I have committed an error. When repositoryFacade is got from getShar
I have a project structure like this : Here, IApplicationDbContext.cs interface defined in Application layer and it's implementation is done in Infrastructure
While studying DDD I'm wondering why the Domain model need to define interfaces for the Infrastructure layer. From my reads I got that a high level (domain mo
We are preparing to build a large scale server application. To model the logic effectively we're planning to use DDD, including the tactical p
I have a multi-tenancy project using mediator and CQRS, for some reason my CRUD from order request are returning this error, I already try refactor my handler s