XTDB 2.0 is Now Generally Available

We're live! 🚀

We're really pleased to announce the generally-available release of XTDB 2.0.0:

• 'HTAP': 'hybrid transactional/analytical processing', OLTP + OLAP - reduce your dependency on fragile networks of ETL jobs.
• Full, across-time queries: using SQL:2011's bitemporal primitives and/or 'XTQL' to answer "what did we know, and when?".
• No history/audit tables, triggers required: use it as a regular update-in-place database (you're free to UPDATE and DELETE normally again!), safe in the knowledge that your history is there when you need it.
• Zero-cost, full database snapshots: immediately go back to any point in time without needing to schedule or store periodic snapshots/copies.
• Postgres wire-compatible: use all of your existing client drivers (e.g. psql, JDBC, Postgres.js, VS Code's SQLTools) and BI tooling (e.g. Metabase).
• Decoupled storage/compute: current/frequently accessed data stays hot on the compute nodes; historical data stays available on cheap, durable, commodity object storage (e.g. AWS S3).
• Full nested-data support with schema inference: arrays and maps are first-class citizens in XTDB - no distinct JSON type, timestamps-as-strings etc, just insert your documents and we'll infer the schema!
• New columnar storage & query engine, open data format: XTDB's files are in the open Apache Arrow format, optimised for data locality and minimal (de-)serialisation.
• Free and open source: MPL licensed (OSI/FSF approved).

Get started by either:

• heading to https://play.xtdb.com - our online playground where you can try XTDB in your browser
• using the XTDB standalone Docker image, and your usual Postgres tooling:
  docker run -d -p 5432:5432 --name xtdb ghcr.io/xtdb/xtdb:2.0.0 psql -h localhost xtdb

Then:

• To understand more about the value XTDB brings, visit the main XTDB website at https://xtdb.com
• Developer documentation is at https://docs.xtdb.com
• Issues/PRs and the source code are on our GitHub repo, as well as our public forum - subscribe here for release notifications.
• Join us on the XTDB Discord server for community support.
• Email us at [email protected] for bespoke support provided by JUXT, a leading software consultancy.

If you're interested in how this all works under-the-hood, I recently wrote a three-part blog series, "Building a Bitemporal Database":

1. a Taxonomy of Bitemporal Data
2. Bitemporal Resolution
3. Storage

I'd like to take this opportunity to give a massive thanks to everyone who's helped out through the early access programme - our Design Partners, the XTDB open-source community, and, of course, the XTDB team themselves.

If you've any questions or thoughts, please do get in touch - we'd love to hear from you!

James, Jeremy and the XTDB team

For those upgrading from the latest beta, a couple of changes to tell you about:

• We've removed the legacy /status endpoint on the HTTP server - this is now much better served by the metrics available on the healthz server (default: http://xtdb-host:8080/healthz).
• GCP and Azure are out of labs - their Maven group is now com.xtdb (artifacts xtdb-google-cloud and xtdb-azure respectively).
• HTTP server is into labs: com.xtdb.labs:xtdb-http-server, reflecting our development focus on the Postgres wire-compatible API.