Absolutely. Keep in mind that ActorDB actually requires that you supply the sharding key yourself whenever you do a query. It&#x27;s not like, say, Elasticsearch, which shards both reads and writes transparently.<p>Many apps do require large queries that span many &quot;partitions&quot;: For example, listing all of a StackOverflow member&#x27;s contributions across all communities, sorted by time. With ActorDB, you would have to plan for this by denormalizing a bit (biokoda might correct me here): Each community would be an actor with a table of QA items, and each user would also have an actor containing a table listing their own QA items for all communities. Since ActorDB apparently has transactions, you can maintain this duplicate data atomically, though you can&#x27;t maintain foreign-key constraints across actors.