Clojurians Log v2

It is, but we'd recommend client/server for anything 'serious' (for some definition of 'serious' 🙂) Main reasons being: • to not tie the lifecycle of the database nodes to the lifecycle of your applications - chances are you want to deploy your applications much more frequently than a database node, but you probably don't want cleared database caches every time you do • you may want different resource-types for your XTDB nodes than would make sense for your applications - e.g. on AWS, we recommend instance types that have plenty of fast instance storage (i3-class) • XT2 nodes benefit from as much memory as you can give them for local caches - while the minimum reqmt is relatively low, the more you can give them, the better • they also have background compaction processes -these are co-ordinated within the XTDB node so as to not take resources away from queries, but we can't promise the same for if your application is busy