ActorDB is not a distributed clone of MySQL. So yes you must know which actor you are querying. This is why we say it is mainly a database for apps. If your qu

ActorDB is not a distributed clone of MySQL. So yes you must know which actor you are querying. This is why we say it is mainly a database for apps. If your queries are always hitting a specific user, then you make that user into an actor. Fully relational, within an user. There is another data type, which is a KV store. But there you are always operating on keys. With the added functionality compared to most other KV stores is that the value can be structured. You can have multiple columns and tables all tied to a specific key and you can incrementally update the value (most other KV stores only support complete rewrites of value).