<story><title>XTDB 2.x Early Access</title><url>https://www.xtdb.com/v2</url></story><parent_chain></parent_chain><comment><author>lgessler</author><text>I used XTDB on a side project (written in Clojure) a couple years ago and was blown away by something that I think isn&amp;#x27;t even really stressed as a headliner feature for XTDB. That was the ability to treat queries as first-class data. XTDB&amp;#x27;s datalog queries can be provided as just native Clojure data structures, and that allows you to build complex queries using code. What this means is that it&amp;#x27;s much more DRY than copy-pasting and editing SQL templates, there&amp;#x27;s no ORM gumming up your performance and expressivity as your queries get more complex, and there&amp;#x27;s no half-baked implementation of an API for query composition: the _programming language_ is your tool for query composition. I couldn&amp;#x27;t tell you if there are other ways of getting this, as I&amp;#x27;m not really a software engineer anymore, but it was a jaw-dropping experience for me to see how easy it could be to write a database layer, and far and away the best experience I&amp;#x27;ve ever had writing one in any programming language.&lt;p&gt;I suppose what&amp;#x27;s at the heart of this, more than anything, is that Datalog has a near-trivial syntax that can transparently be accommodated by two simple data structures: lists and hash tables. Not so with SQL, whose COBOL-y nature obscures its syntax and makes it less straightforward to represent in everyday data structures.</text></comment>
<story><title>XTDB 2.x Early Access</title><url>https://www.xtdb.com/v2</url></story><parent_chain></parent_chain><comment><author>kevinmershon</author><text>We use XTDB 1 and have a multi replica production instance with about 600GB of data at ~100 million transactions. The biggest problem we have is with minor versions bumping the underlying RocksDB i dex version, requiring a full reindex of the main &amp;quot;golden&amp;quot; data store taking days to weeks.&lt;p&gt;AFAIK this is not solved in XTDB 1. I&amp;#x27;m hoping XTDB 2 provides a better upgrade path for modestly sized databases like ours.</text></comment>