As I pointed out above, that's not the API that would be exposed in an actor model. See in particular the timestamp-based update condition, if you're principally concerned with end-user-caused races.

Less relevant, but message queues in Erlang and related languages are typically in-memory, no DB transaction required.