Pere Diaz

strike, scream and run @tursodatabase

[Pere Diaz @Peristocles1]

@Alan22777231 @penberg @glcst @IrrationalShuma Could you send or post in the issue a reproducer if you don't mind?

[Pere Diaz @Peristocles1]

@glcst @DNAutics I've been held hostage under the @glcst and @penberg regime for far too long. After long free labor I got a job, truly disgusting. Thankfully AI will replace us all so we never have to work again.

[Glauber Costa @glcst]

We at @tursodatabase are ecstatic to announce today the private beta of the new generation of the Turso Cloud.

The Turso Cloud has been a great destination for builders building agents, that recognize that agents need millions of databases, and that the SQLite file-based approach is the way to achieve that at scale.

But at the same time, SQLite comes packed with limitations. Over a year ago, @penberg had a bright and bold idea - perhaps the only good idea he had in his life - what if we rewrote SQLite entirely? If we do that, our Cloud can keep the unmatched database density at scale it has today, but without that ceiling that makes SQLite be seen as a temporary solution.

Fast forward to today, Turso, our rewrite of SQLite, is right around the corner. Concurrent Writes are here, and many other features.

And select teams will be able to run it first in the Turso Cloud: query it directly, or use it to sync your Turso databases. All of that, with enterprise-grade encryption, and running in your own cloud account.

Link 👇

[Pekka Enberg @penberg]

We’re putting Turso in Turso Cloud with concurrent writes and more. Private beta waitlist here: https://t.co/NN36rsvCmi

[Glauber Costa @glcst]

Super excited to announce that @tursodatabase is joining the Stripe Projects developer preview giving developers and AI agents a clean, deterministic way to provision real Turso Cloud databases straight from the terminal. No dashboard hopping, no brittle scripts, no manual key handling.

Just fast, secure, and agent‑ready provisioning SQLite databases available in seconds. Infinite databases for infinite agents =)

[Glauber Costa @glcst]

Unlimited agents with unlimited databases.

Excited to see https://t.co/4NZNcwFipR take off

[Pere Diaz @Peristocles1]

@samlambert I've been cracking my neck since I was 7 years old from all angles and force. All good (for now)

[Aaron Francis @aarondfrancis]

Rewriting SQLite... from prison!

In this interview I talked with @PThorpe92, who is a full time software engineer and currently incarcerated for non-violent offenses.

He's helping @tursodatabase rewrite SQLite from scratch.

It's an inspiring story.

https://t.co/ezVRAOIsTi

[Pere Diaz @Peristocles1]

@notrab @tursodatabase ❤️

[Glauber Costa @glcst]

Turso now supports *LIVE* materialized views! Based on a framework of Incremental Computation, LVM are Materialized Views that are updated in real time, by looking only at the delta of the changes instead of the whole table.

That means you can have terabytes of data and a very complex query: once the data in the tables changes, the MV are updated right away.

We are building Turso because we think databases will be EVERYWHERE. And LVM allows Turso to be used in front of streaming systems, in reactive environments, giving humans and agents access to fresh, live data to make quality decisions in real time.

Read more 👇

[Pekka Enberg @penberg]

We started with "embedded replicas" in libSQL, which allowed you to read locally, but you had write remotely. We introduced offline mode earlier this year, but @SivukhinN took it to another level by lifting the single-writer limitation! 🔥

https://t.co/r4hF9rAKE1

[Pekka Enberg @penberg]

Turso (the database) builds for Wasm, but that's only half of the story of running a database in the browser. Nice work from @SivukhinN and @notrab to make this happen! 👏👏👏

https://t.co/SBAnmp70yY

[Glauber Costa @glcst]

Day 2 of @tursodatabase beta week is here and... encryption!

We believe that with AI capturing even more data, and more private data, we will need to have end-to-end encryption everywhere. SQLite doesn't ship with native encryption.

Turso fixes that, by having fully integrated encryption at the page level. The implementation adds only as little as 6% overhead, with improvements to come.

Read more 👇

[Glauber Costa @glcst]

Today, @tursodatabase hits its first beta release. And in the beta, you will have experimental support for our most anticipated feature: concurrent writes.

SQLite is a beast. It is the fastest database out there. But users struggle with concurrent writes not being possible. With Concurrent writes in Turso, we get to 4x the throughput of SQLite for writes.

SQLite is almost everywhere. But lack of concurrent writes prevents it from being used in high-volume data ingestion workloads. Even at low throughput, SQLite users report having issues with the dreaded "database is locked" issue with multiple writers.

Turso fixes this by adding MVCC (Multi-Version Concurrency Control). Transactions can proceed in parallel if there are no conflicts, only serializing if there are conflicts.

The work on MVCC is very early and in the next months we will still evolve a lot. As usual with our Open Contribution community, we want that evolution to happen together with you all.

Read more 👇

[Pekka Enberg @penberg]

Nice ship from @iavins to bring fast, integrated encryption at rest to @tursodatabase! 👏👏👏

https://t.co/9d7IsTUV7u

[Pekka Enberg @penberg]

Excited to have the early preview of BEGIN CONCURRENT in Turso finally out! A pretty massive effort by @Peristocles1, @jussisaur, and myself, but also @sarna_dev and @iavins back in the day when we attempting to do this in SQLite!

https://t.co/XuSTe06g1K

[Pere Diaz @Peristocles1]

@penberg Good times when we didn't have clippy

[Pere Diaz @Peristocles1]

@penberg I'm done, not even `cargo fmt` did the job. Going to the gym.

[Pere Diaz @Peristocles1]

@penberg it took longer than 20 minutes, I had to come up with a commit name