alt Hacker NewsThe key feature of Erlang-style actors is that messages are enqueued and processed serially, thus eliminating race conditions of this type.
The key feature of Erlang-style actors is that messages are enqueued and processed serially, thus eliminating race conditions of this type.
If the read and the write are separate messages, i.e. the computation of the modified value happens sender-side, as in the parent example, then I don’t see how a serializing queue prevents the race condition, for two concurrent senders (clients). For that you need transactions, exactly like a database.