In my view the executive (supervisor) both starts and completes the saga, yes. But it's also possible that some long-running process actually never completes....
... Indeed, we can't have an aggregate commit a transaction on its own. I'm still trying to workout where actors might fit into DDD though. The main benefits...
Hi guys, DDD was coined by an american guy and most (if not all) of the programming languages we usually use are in english. How much of you guys, do use your...
I am not sure I understand why using an actor to control domain model task management is considered to be negative. I know that your goal is to share nothing,...
You can consider each Aggregate an Actor. Share nothing comes from the fact that state changes are pushed async, not shared (events), so is up to the observer...
Hi, ... 1) By definition of Aggregates to share consistency boundaries, hence no state is shared 2) Make a repository object for each Aggregate. They work as...
This is a very interesting discussion. It's just that I don't see how an aggregate instance itself can be an actor unless you keep every aggregate instance in...
Most teams I work with will go through and use english overall but keep native language for domain specific terms that do not translate well. ... -- Le doute...
Hi, I think it really depends how one sees things. ... If an object is only valid if persisted then short term memory aka RAM, is irrelevant. Your main memory...
... It's more that the object must be persisted to be persistent :) Josh's original post was discussing Scala and Akka, or at least the blog he referenced was....
... Yes, I'm currently prototyping in Scala with Akka, but this seems to be an area that I haven't found much info on in general - how share nothing and actors...
Hi, ... Yes, but in such replication context there is only one active node, the others are dormant. I'm ok with replication in that way. I don't see...
... It is true that the aggregate boundary means that the object's internals are not shared by any others. However, it does not prevent a user from modifying...
... True, but a single actor can only be used by one thread at a time. Messages are received and processed serially. It's it is because of this that the actor...
Yes, it is the actor framework that will serializes messages into the actor's maibox. It is in this way that actors are threadsafe since the only way to...
As long as one actor will ever use a given aggregate instance, and all UI requests work through actors. Both situations reduce performance through scalability....
If you use CQRS + ES an aggregate sure starts sounding like an actor ... ... -- Le doute n'est pas une condition agréable, mais la certitude est absurde. If...
I'm under the impression that ad long as we use aggregates an reads do not block transactions one is in the realm of the Actor Model. Sent from my iPhone ... ...
Hi, In my experience it depends on the domain and the language used by domain experts. In some domains, e.g telco rating and billing, english terms are used...
Yes, what he describes is what I have been discussing. As far as I can tell his approach doesn't make the aggregate itself the actor. The actor receives an...
Hi guys and thanks for your feedbacks ! So for domain objects, most of you use the native language of domain experts to name your classes but what about method...
