4 ms·
At first I assumed this would lock all touched state across all touched actors such that you get the same kind of cross table-row locking guarantees a SQL call
by jayd16 6y ago
At first I assumed this would lock all touched state across all touched actors such that you get the same kind of cross table-row locking guarantees a SQL call would give you
...but it seems like its still an open question in the RFC?
- dwaite 6y agoactor state is meant to be read and modified only by the actor itself, which operates off of its own message mailbox (e.g. event queue). I would expect actors to operate on their own state and on immutable data, and things such as transactional data coordination to be separate. That said, I don't have nearly the experience with actors as many on HN - are you thinking of a particular actor-based system w.r.t touched state?