Individual actors are individual units of replication. What one actor is writing is concurrent to what another is doing. Read/write calls to an actor are seque

Individual actors are individual units of replication. What one actor is writing is concurrent to what another is doing. Read/write calls to an actor are sequential. I'm quite sure this is how other KV stores like Riak do as well. They have X units per server and those process requests sequentially. Their actual concurrency is basically how many units per server are running. They may interleave reads/writes per node or they may not. ActorDB does not allow reads while a write is in progress. It is quite possible we will optimize this part in the future as it is quite doable.