We don't provide anything specific to Crux for this task at the moment - but what were you imagining? Dumping everything to a zipped directory of edn files?

> I guess you can back up using specific ways based on each backend exactly this - idea is that we lean on their much more established practices likewise for deployment and monitoring, too 🙂

@U899JBRPF yes, maybe or maybe transit to save a bit of space… I guess it would facilitate switching to a different backend too

cool, yes it certainly would help with that migration also - we are tracking that as an issue here https://github.com/juxt/crux/issues/1386

@U899JBRPF thank you 🙂

Hey! entity avoids the query engine entirely and hits the document cache directly, so this will always be fastest, except in cases where your document is massive and you only need a few key-values from it. Querying (`q`) via an eid is going to be faster than looking up an entity by some unique a-v combination, since otherwise you need at least one extra join to resolve the a-v, which means an extra KV lookup under-the-hood. However, any performance difference will very likely be negligible compared to other aspects of your domain modelling complexity 🙂