I wonder why other providers don't use metal ssd sync replication technique that planetscale uses? Most of them just default to EBS.
My interest in it peaked when I heard about NVMe over Fabrics (NVMe/TCP) and SPDK from Xata[1] and apparently with that performance is as good as planetscale metal, but planetscale found their methodology flawed[2] and they Xata never responded.
[1] https://xata.io/blog/reaction-to-the-planetscale-postgresql-...
I'm honestly confused why local nvme disks haven't become the standard for cloud offerings a long time ago.
Aiven (not working for them, just a happy client) started offering local nvme disks for their postgres service in 2017. (https://aiven.io/blog/larger-and-faster-aiven-postgresql-pla...)
Back then I was sure it was only a matter of time for other hosted database providers to move on from EBS. But until Planetscale made a lot of noise about Metal no one seemed to bother.
Indeed we're doing fewer new features (and haven't posted to the posts page in a long time, as you noticed).
But it's still maintained, folks are still using it, if anyone finds bugs in simple-to-moderate queries then we'll fix them.
LLMs probably took a bit of the wind out of our sails for making this "the new standard". But I still think it's a really nice language and interface; if the world changed again such that it became more widely useful, I'd jump to spending lots of time on it again.
I just found out about PRQL yesterday! I was looking for a query language that is more token efficient and easier to reason about for LLMs than SQL.
PRQL looks amazing for data analytics agents. Our first few test are quite promising.
I also really appreciate the python bindings. We don't give our agent direct access to the database, we only provide the schema information. The python api makes it super easy to convert a query into an AST, which lets us do some basic offline validation of table names, etc.