Domain Driven Design – designing Aggregate Roots
Imagine you’re designing an application for organizing Workshops.
Workshop itself is quite complicated – it acts as a state machine with multiple possible states and transitions between them.
Domain Driven Design – designing Aggregate Roots
Imagine you’re designing an application for organizing Workshops.
Workshop itself is quite complicated – it acts as a state machine with multiple possible states and transitions between them.
Domain Driven Design – designing Aggregate Roots
Imagine you’re designing an application for organizing Workshops.
Workshop itself is quite complicated – it acts as a state machine with multiple possible states and transitions between them.
Domain Driven Design – designing Aggregate Roots
Imagine you’re designing an application for organizing Workshops.
Workshop itself is quite complicated – it acts as a state machine with multiple possible states and transitions between them.
Domain Driven Design – designing Aggregate Roots
Imagine you’re designing an application for organizing Workshops.
Workshop itself is quite complicated – it acts as a state machine with multiple possible states and transitions between them.
Is it necessary anymore to extract logic from API controllers?
I’ve been working in MVC web frameworks since its they started getting popular with RoR and ASP.NET MVC. I have always been careful to never put “business logic” on my controllers since that couples the framework with the logic. These days, like many of you, I’m not really using the MVC part of my framework, since I’m not returning “views” and framework artifacts. Instead, I’m just using routes to controller actions to build API’s that return xml or json.
Is it necessary anymore to extract logic from API controllers?
I’ve been working in MVC web frameworks since its they started getting popular with RoR and ASP.NET MVC. I have always been careful to never put “business logic” on my controllers since that couples the framework with the logic. These days, like many of you, I’m not really using the MVC part of my framework, since I’m not returning “views” and framework artifacts. Instead, I’m just using routes to controller actions to build API’s that return xml or json.
CQRS – How can a command properly validate when queries are required?
I’m aware that this question has been asked several times, but I have some concerns regarding querying from the write side that I don’t see addressed in the already existing questions, more especifically regarding eventual consistency in the command model.
CQRS: Multiple entry points for a single command
I’m trying to follow the Clean Architecture and CQRS within an application that, let’s say, create a product.
CQRS: Multiple entry points for a single command
I’m trying to follow the Clean Architecture and CQRS within an application that, let’s say, create a product.