There is one master per actor. An actor lives within a cluster. As long as a majority of configured servers are accessible, writes will succeed. All queries (r

There is one master per actor. An actor lives within a cluster. As long as a majority of configured servers are accessible, writes will succeed. All queries (reads and writes) go through the master and are not committed if master does not reach a majority of configured servers in the cluster. Individual actors are not meant to be scalable. They are meant to be fast enough. For instance if you were to create your own news.ycombinator.com an actor would be this entire conversation tree. Sqlite would be sufficient. You don't need concurrency on a per thread level. ActorDB provides a global uniqueid generation feature (independent of sqlite).