ActorDB is very cool, but from what I gather it&#x27;s — at least nominally — designed to work with many small databases (one per &quot;actor&quot;) as opposed one large one, and that the constraints it puts on the query model means you have to carefully design your data model to be heavily compartmentalized from the beginning. It also poses some problems for database-wide queries, which have to fan out to every separate actor database. Whereas rqlite acts like one single SQLite instance, and can work with existing schemas.<p>Please do correct me if I&#x27;m wrong. Would ActorDB be happy and perform well with, say, just one actor?