The MariaDB approach vs the DB Trail for MySQL approach: Comparing time-travel
Two ways to keep database history: inline system versioning, or an external change-data-capture index on a separate machine. This is not a speed contest. It is…
Archive
DB Trail Open Source now has a UI
DB Trail now has a web console. That is the short version 🙂 For as long as dbtrail has existed, you drove it from the command line:…
Rate Limiting (Throttle) for MySQL with ProxySQL and Bintrail
Back in 2020 I wrote about rate limiting writes to MySQL with ProxySQL. The main idea is still valid, but two things changed enough to write…
MySQL Time-Travel with near-ZERO overhead: How bintrail skips the write load
A reader asked four operations-grade questions about Time Travel SQL. Here is how bintrail handles multi-TB tables, retention, monitoring, and partitioning - and how it differs…
Time-travel SQL for MySQL, finally
A time ago I argued MySQL is the only major OLTP database without time-travel queries. Here’s what’s changed. Last month I mapped out how every major…
For a Database, survive used to mean “The server stays up”. With AI Agents, that’s not enough anymore
One of the 3 promise that a database do is: I will Survive. Traditionally it was physical: disk, memory, replication, OOM. The hardware side. With agents,…
An AI Agent is talking to your MySQL. And the database doesn’t know who is that! – Agent Era, Part 3
You’re still running agents against MySQL. So am I. Last time we walked through what happens when an agent doesn’t understand the query it’s running. This…
Three Promises in the Agent Era, Part 2: Agents on production MySQL are fine. Until they’re not.
You’re running agents against MySQL. So am I. It’s where we are. Sooner or later you’re going to be recovering data because of something one of…
Three Promises in the Agent Era, Part 1: The Frame, Reread
The series: A few time ago I wrote that a database does three things: It executes queries. It manages relationships. It survives the physical machine it…