REST Service and CQRS
I am struggling with architecture on a new project. I am using the following patterns/technology.
REST Service and CQRS
I am struggling with architecture on a new project. I am using the following patterns/technology.
Entities (DDD) when using CQRS on Akka
When using Akka, CQRS style, is still there a place for Entities?
Managing non-domain application behaviour in CQRS
Here’s a scenario.
Encapsulate one business story/use case in one class?
I don’t like classes like *Service, with bunch of business methods – aka anemic model. I was thinking, instead, to have a class per use case. This was inspired (if not the same) from CQRS. Even if we are not using event sourcing, I believe that this kind of encapsulation would make sense. Then the service layer (application layer) would simple consist of commands that user can instantiate and pass to some executer.
What is eventual consistency?
I’ve heard people talking about “eventual consistency” (for example in this question and this answer).
How to model parallel processes (in a Bounded Context) with the same data store?
The situation. Let’s say a background process puts stuff into data containers. It runs all the time, observes system events, and populates the data accordingly.
How to model parallel processes (in a Bounded Context) with the same data store?
The situation. Let’s say a background process puts stuff into data containers. It runs all the time, observes system events, and populates the data accordingly.
How to model parallel processes (in a Bounded Context) with the same data store?
The situation. Let’s say a background process puts stuff into data containers. It runs all the time, observes system events, and populates the data accordingly.
What layer generates commands for dependent services?
Our business works with truck drivers making pickups/deliveries of containers. The location of containers needs to be tracked.