"Handling the element of time in SQL has been a challenge since it was created" "current databases require you to manually insert time values that track when a data item was added, when it became valid, and when it became invalid" Reflections by @Intellyx's Eric Newcomer [1/2]

🎁 XTDB 2.1 is now released 🎁 Thanks to the decoupled, shared storage architecture you can now dynamically ATTACH secondary databases with full read-write abilities and run queries across your Data Mesh with ease:

Wrote a blog post about continuation-passing style in @xtdb_com. https://t.co/bmDoZefCeF

The theme of @CMUDB's ongoing Future Data Systems seminar series is "what should a database system look like in the future to handle more of our past so we never forget" - clearly I'm biased, but the answer has to be @xtdb_com ! Join us live on 24th November to learn more...

this week on the unikernel application spotlight we go time traveling with @xtdb_com

Monday Sept 22nd is the start of @CMUDB's new seminar series: Future Data Systems @SamArchDB + @pateljm + I are hosting speakers building vanguard datalake / lakehouse systems. Mondays @ 4:30pm ET via Zoom. Open to the public. Videos posted to YouTube: https://t.co/yv1XkGc5jw

Fall 2025 Seminar Schedule: Sep 22: @ApacheIceberg Sep 29: @ApacheHudi / @Onehousehq Oct 06: @motherduck Oct 13: @SpiralDB's @vortexdotdev Oct 27: @SingleStoreDB Nov 03: @DeltaLakeOSS Nov 10: @mooncakelabs Nov 17: @FireboltHQ Nov 24: @xtdb_com Dec 01: @apachepolaris / @Snowflake

What if there was a Clojure library like re-frame, but all state was server-side in an @xtdb_com temporal DB? What if the debugging tools took full advantage of this? SQL subs, SQL reactions, SQL debugging, SQL logs (clj, cljs, js) - all immutable with '1st class' time...

Reactive SQL tables & time-travel. Like peanut butter & jelly. @xtdb_com

"[D]ata compliance assurance is only getting more complicated – and the more complicated it gets, the greater the XTDB value proposition" - @TheEbizWizard https://t.co/Gc6TJ0gbtT

@narayanarjun For details on the upcoming events

We're running a series of XTDB v2 pre-launch events (informal chats on our Discord server) over the next few weeks. Later today we're speaking with @narayanarjun about as-of joins and database architecture - come join!

Great way to mess around with temporal DBs like @xtdb_com.

In the build up to an official XTDB v2 release we are running a series of informal chats on our Discord server - come join! This Friday we're speaking with @narayanarjun who has battled many times with as-of chaos during his time at Materialize - see

"It would be desirable to arrange the events so that a look into our data base will show the latest surface of the event space. At the same time it should be possible to penetrate beyond this surface along the lifelines into the past." -- UPDATE RECONSIDERED (1977)

@bbgatch Here’s one I used last year. The representation is called Datalog. I used it with the XTDB database.

XTDB 2.0.0-beta7 is now available! The release includes a new indexing strategy specifically for handling time-series data:

Am honored to (virtually) sit down with @malcolmsparks & @refset on the @juxtpro podcast. Chatting about Clojure, SQL, Rabbit, end-user programming, visual tools, etc. https://t.co/KS5JT39Fer

Join us LIVE for a 1-hour session on 19 Feb (tomorrow!) at 1500 UTC, where @refset will give a tour of the latest developments in v2 ahead of the General Availability launch, which is just a few weeks away 🚀 https://t.co/2BLWYpXMfY

SW Engineer @mpisanko shares insights on integrating @xtdb_com – an open source bitemporal database – into @FINOSFoundation TraderX trading app. Adding temporal 'sliders' shows XTDB's "time-travel" feature, enabling to navigate and visualize data changes

v2.0.0-beta6 is out today 🚀 Lots of bug fixing and resilience improvements in this one. Next up is beta7, with improved support for time series data - we'll finally be able to settle an age old debate: "how is XTDB different to a time series database?" https://t.co/8lPKvJftUk