Alex Miller
alexmillerdb.bsky.social
Alex Miller
@alexmillerdb.bsky.social
Database Papers as a Service
I had also assumed that SAL drives replication to page servers so that the compute knows exactly which version a page server is caught up to so that it can avoid sending reads to servers which don’t have the data yet. They wanted to batch updates to page servers, which adds replication delay, so…
November 9, 2025 at 6:04 AM
I’m surprised you especially weren’t offended by their “our reconfiguration-based replication protocol has 100% availability” argument :p
November 9, 2025 at 6:04 AM
October 20, 2025 at 5:33 PM
I'd even settle for someone just updating the number on Rusty's nearing 20 year old "To BLOB or Not To BLOB"
October 14, 2025 at 10:54 PM
Kuzu just folded/pivoted.
> Kuzu is working on something new! We will no longer be actively supporting KuzuDB.
is on kuzudb.com

Me thinking a startup has promising tech has so far been a kiss of death to the company. An "Inverse Alex's Tech Opinions" fund might be very profitable. 🤔
October 10, 2025 at 6:11 PM
Cool!!! I'll give it a try sometime over the next few days when I have a good chunk of time and let you know how it goes!
October 10, 2025 at 6:00 PM
swiftwave.org looked interesting for small and simple self hosting
SwiftWave
SwiftWave is a self-hosted open source lightweight PaaS solution. It is designed to be easy to use and deploy applications.
swiftwave.org
September 30, 2025 at 8:19 PM
I will note that “scan sharing” seems specifically inter-query. If you have a single query that scans the same table multiple times and you want to coalesce that to scanning only once, that seems to be classified under subplan reuse instead?
E.g. link.springer.com/content/pdf/...
link.springer.com
September 29, 2025 at 12:50 AM
I think you’re talking about scan sharing? 15721.courses.cs.cmu.edu/spring2016/s...

I don’t know the OG citation for this. Andy cites graphs from 15721.courses.cs.cmu.edu/spring2016/p... and ir.cwi.nl/pub/12225/12... also looks pretty reasonable.
September 28, 2025 at 8:28 PM
Err, I mean, I guess Yugabyte is also not linearizable and snapshot isolation, but just because of HLCs being inaccurate. LeanXcale is very intentionally not linearizable, and they mention that you have to do some extra work to even get session consistency out of it.
September 23, 2025 at 7:17 AM
There’s a database startup called leanXcale which is the only non-linearizable snapshot isolation system that I know of. www.sciencedirect.com/science/arti... is a pretty decent overview, but there’s a YouTube talk somewhere too.
Elastic scalable transaction processing in LeanXcale
Scaling ACID transactions in a cloud database is hard, and providing elastic scalability even harder. In this paper, we present our solution for elast…
www.sciencedirect.com
September 23, 2025 at 7:14 AM
Do you think he’s just been “I told you so”-ing people since 1964? 😂
September 22, 2025 at 9:38 PM
If you’re not ramped up on WCOJ algorithms, a lot of the papers are complicated to get through, but I thought TreeTracker Join arxiv.org/pdf/2403.01631 was pretty comprehensible and shows the minimal difference for NLJ. Or see justinjaffray.com/a-gentle-ish...
September 21, 2025 at 4:56 PM
Even as a disliker of YouTube videos as a way to learn things, I found www.youtube.com/watch?v=-XmJ... easier to understand than the paper www.cs.ox.ac.uk/dan.olteanu/... for factorized database work

Extending SQL to Return a Subdatabase dl.acm.org/doi/pdf/10.1... also seems related?
September 21, 2025 at 4:56 PM