5
votes
Is the Actor Model an alternative to transactions?
You state correctly that transactions and locking are needed to deal with shared mutable state. And also that in an actor system, there is no shared mutable state. So it seems you've already answered ...
2
votes
Akka Event Sourcing - how to create Actor per Entity
You want to look at Akka Cluster Sharding. This complements Akka Persistence to distribute the instances that are currently kept in memory in the cluster and manage their lifecycle.
Also keep in ...
2
votes
How to implement semantics of serializability in eventually consistent system?
The most straight forward approach is probably to distinguish verified emails from unverified emails within your model, and have a single actor responsible for verifying a given email address.
(The ...
2
votes
Can the actor model replace a database?
An actor model is a way of thinking about concurrency, so it "replaces" other ways of thinking about concurrency, like async/await, or promises, or threads and locks, etc.
So think of where ...
2
votes
Accepted
Shared immutable state between actors
“State” in this context always implies mutability. Thus, “immutable state” isn't state, it's just immutable data. There is no general problem with sharing immutable data structures between actors. If ...
1
vote
Processing messages in parallel with Kafka & Akka
I don't know about reference architectures, but here are some more approaches:
Approach #3: at least once semantics
Hold the current batch of kafka messages in memory in the actor that reads from ...
1
vote
RMI vs APIs vs Akka Cluster
It's been many years since I've used Akka and have never had to deal with it clustered, but some quick research suggests Akka Scheduler isn't really meant for long-term jobs like this, and that you ...
1
vote
How to implement semantics of serializability in eventually consistent system?
This is known as set validation.
At some point in time, sooner or later, you will have to serialize this checking, so scalability will be affected for sure. You still get to choose when: before you ...
1
vote
Is the actor model suited for an application dealing with elapsed time?
There is nothing fundamentally problematic with using the actor model for this and supervision is very helpful in creating stable distributed systems. With that said, you still have to design the ...
1
vote
Entities (DDD) when using CQRS on Akka
Yes. In DDD an aggregate contains an aggregate root which is an entity, and one or more other objects which themselves may be both value objects and other entities (chapter 6 in Evans' blue book). How ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
akka × 34actor-model × 15
scala × 10
java × 4
domain-driven-design × 3
erlang × 3
design-patterns × 2
.net × 2
multithreading × 2
concurrency × 2
spring × 2
distributed-system × 2
messaging × 2
locks × 2
design × 1
architecture × 1
api × 1
refactoring × 1
node.js × 1
error-handling × 1
cqrs × 1
event-sourcing × 1
wpf × 1
message-queue × 1
nosql × 1