Pleasure working on it with you! I'm looking forward to my copies. :)
04.03.2026 19:02
👍 9
🔁 0
💬 1
📌 0
Pleasure working on it with you! I'm looking forward to my copies. :)
A print copy of Designing Data-Intensive Applications, 2nd edition
Just received my author copies of the second edition of DDIA! After years of seeing it only on-screen, holding the final print book in hand is very special. @chris.blue
Feedback need: SlateDB's Python API uses pyo3, which supports Python/Rust async integration. The other bindings use slatedb-c (C FFI ABI), which is sync. Ideally, I want all bindings use one layer (FFI) to simplify maintenance. Should I ditch pyo3 and async Python support, tho?
"A background job queueing system built on top of object storage via slatedb" 🤩
Was just talking about the need for this with @almog.xyz today!
github.com/gadget-inc/s...
To serve, stick around.
Excited to enable pipelining by default in s2-lite with this upgrade! Expect lower latency and higher throughput.
github.com/s2-streamsto...
Finally, we published an official Java binding on maven central:
central.sonatype.com/artifact/io....
We did a full rewrite of slatedb-c to make this possible. All official bindings will use slatedb-c's FFI bindings moving forward. This gives us a single stable foundation.
A new slatedb-txn-obj crate is now available. Use it to implement transactional objects with epoch-based fencing, retries, conflict merging. It's a critical component of SlateDB, and it's now available to everyone.
crates.io/crates/slate...
The `DbReader` also got some attention:
- Added `DbReaderBuilder`
- Readers now support on-disk object store file caching
- Readers can preload (warm) caches
- WAL object store support
Writes now return a `WriteHandle` that contains the sequence number of the write. This is a first step in adopting time-travel reads on SlateDB. Users can also tie sequence numbers to other identifiers such as PostgreSQL LSNs or Kafka offsets.
slatedb.io/rfcs/0018-ex...
We're also exposing more database lifecycle information. Users can now call `db.status()` and `db.subscribe()` to check database status and receive notifications when status updates occur. `db.status()` can also be used as a health check.
SlateDB now offers a `WalReader`. Users can now write low latency write-ahead log (WAL) consumers to implement change data capture (CDC) on SlateDB databases.
slatedb.io/docs/design/...
Users can now write compaction filters to mutate or delete data during compaction. Importantly, this feature allows users to implement custom retention and truncation policies for their data.
slatedb.io/rfcs/0017-co...
SlateDB 0.11.0 is out! We had 5 new RFCs, 10 new contributors, and 3 new language bindings. This is a big release with a bunch of improvements and new features. 🧵
Serverless is a mess. Persistent VMs for the win. blog.exe.dev/persistent
“Gradually, then suddenly.” That’s how adoption works when you’re building something new. Opendata is still "gradually" but 100 stars with $0 spent on marketing is a good start. Back to building! github.com/opendata-oss...
Tolja
Book cover of "Designing Data-Intensive Applications, 2nd edition". It has a similar wild boar on the cover as the first edition, but it uses O'Reilly's new cover design, and the boar is now slightly colourised.
The second edition of Designing Data-Intensive Applications, by myself and @chris.blue, is finished and sent off to the printers! Ebooks should be available in the next week, and print books in 3–4 weeks. Sigh of relief. 😅
(BTW, this is a good opportunity to support your favourite local bookshop!)
We (@chris.blue and I) did an interview for the @antithesis.com Bug Bash podcast. It was an interesting discussion!
We have landed on an open source monorepo for the Rust SDK, CLI, and s2-lite github.com/s2-streamsto...
> Rimio is a lightweight write-back cache that accelerates object-native systems (SlateDB, ZeroFS, JuiceFS, NeonDB, Greptime, Databend, WarpStream, Thanos, etc.) for edge and on-prem clusters with minimal operational overhead.
🤩
github.com/flaneur2020/...
There could be a pretty nice interregnum where there are no humanoid bots, but the internet (as we know it) is busted. Could be a re-awakening where humans turn away from virtual/online spaces to physical spaces and the real world again.
And again we will probably try to detect them in some way, which kinda sets up the same dynamic as in the book/movie.
Taking this a step farther, when robots get good enough, it makes me wonder if physical space will kinda go the same way. Things could end up quite similar to blade runner, where humanoid robots look similar enough that we can’t tell the diff.
But of course it’ll be impossible to know if you’re actually interacting with humans since they can always turn their computer over to a bot after human verification. So I kinda feel like public internet as it existed is doomed.
Humans will probably try to create separate spaces to interact with actual humans. Private discord chans, private sites, human verification, etc.
I’m reading the blade runner book right now (do androids dream of electric sheep) and it got me thinking. The internet is infested by bots. I kind of feel in the long run that the public internet will be bot-only, or largely bot stuff and a bit of human stuff.
Apple purchased KuzuDB.
ladybugdb.com is the fork & continue project, but I think there’s a slightly different roadmap to be more object storage integrated
