Clojurians Log v2

It's blog day 📝 🚀 part 2 of "Building a Bitemporal Index": "Bitemporal Resolution" I've promised for a while to write up how XT's bitemporal magic works - well, here it is ☺️

Just in case folks here hadn't seen it advertised anywhere else already, JUXT is running an invite-only 'fintech' conference in London next month (12th June): https://www.juxt.pro/xt25/ Clojure is not the focus of the event but certainly will be discussed in a couple of talks. XTDB will feature lightly in the agenda also. Please fill in the form if you'd be interested to attend and think you might benefit from the content/networking. Recordings will be available online afterwards in any case. Unfortunately I won't be there myself due to the imminent arrival of a new baby(!), however James and others will be there to meet and chat about XTDB 🙂

🚨 Anyone here using the XTDB Clojure API for a remote (HTTP) XTDB node (`xtdb.client` namespace)? 🙋 In the next release, we're looking to replace the underlying implementation here with one that uses the Postgres-compatible protocol instead. This'd be a breaking change - in your infrastructure, you'd need to expose the pgwire port rather than/in addition to the HTTP port to continue using the Clojure API client. This is because the Postgres server is starting to move ahead of the HTTP API (due to the XT usage that we're aware of). We will likely keep the HTTP API for simpler use cases (e.g. single queries, or putting maps) but the Postgres API (either via next.jdbc or our xtdb.api helpers) will become our recommended default approach. (If you're connecting to HTTP directly - i.e. not using our client - then this won't affect you)