Software engineering, distributed systems, databases, and the teams that build them
Software engineering, distributed systems, databases, and the teams that build them
Last week I started using some of the new coding agents properly. Not in a careful, experimental way, but properly — for three days on rqlite. Claude Code. Copilot CLI. Tools I had yet to fully integrate into how I write software.
Continue reading “The source code was the moat. But not anymore”
While working with Claude Code, I quickly needed it to operate on multiple versions of the rqlite codebase at the same time. Cloning the repository repeatedly would have worked, but it felt wasteful.
After many months of direct ChatGPT use, I’ve finally started coding with the help of Copilot and Claude Code. It’s definitely an intriguing experience. The biggest difference so far? I’m going to hit my Claude Code Pro limits pretty quickly, whereas my Copilot Premium Requests are far from exhausted.
I’ve been surprised by – and enjoy – one aspect of using large language models more than any other.
They often put into words things I have long understood, but could not write down clearly. When that happens, it feels less like learning something new and more like recognition. A kind of “ok, yeah” moment.
Continue reading “Why talking to LLMs has improved my thinking”
I sometimes read commentary about large software companies and notice a recurring pattern. People correctly identify real characteristics of large organizations, criticize them, but show little appreciation for why those characteristics exist in the first place.
Continue reading “Common misunderstandings about large software companies”
I work as an Engineering Manager at Google, and my teams practice a simple habit – we book all meetings to start at five minutes past the hour (or half hour).
rqlite is a lightweight, open-source, distributed relational database built on SQLite and Raft.
Versions 9.3.5 through 9.3.10 focus on internal correctness and operational robustness, particularly around Raft snapshotting, WAL handling, and testing. These releases also include improvements to logging, the rqlite shell, and routine dependency upgrades, including a new SQLite release.
Continue reading “rqlite 9.3.5 to 9.3.10: Snapshot Robustness, WAL Handling, and Shell Improvements”
rqlite is a lightweight, open-source, distributed relational database built on SQLite and Raft.
Versions 9.3.1 through 9.3.4 deliver a set of targeted fixes and internal improvements, most of them aimed at code quality, security posture, and correctness. The only user-facing operational change is that the official Docker image now runs the rqlite daemon as a non-root user.
rqlite is a lightweight, user-friendly, distributed relational database. It’s written in Go, employs Raft for distributed consensus, and uses SQLite as its storage engine.
The newly released rqlite 9.2 introduces a major improvement to startup performance – nodes can now resume from where they left off, instead of rebuilding their state from scratch on every restart. This change means that even if a node manages gigabytes of SQLite data, it can come back online almost instantly, with startup time no longer proportional to dataset size.
In this post, I’ll explore why this change matters, how it was implemented on top of the existing Raft system and SQLite WAL, and what it says about rqlite’s evolution.
Continue reading “Balancing SQLite’s WAL, SYNCHRONOUS=OFF, and fsync for fast rqlite recovery”
rqlite
is a lightweight, open-source distributed relational database implemented in Go, and which uses SQLite as its storage engine.
rqlite container images are now mirrored to GitHub Container Registry (GHCR). Images on Docker Hub and GHCR carry the same tags and digests; you can pull from either registry based on your preferences or network policy. This change should improve reliability and make it easier to integrate rqlite into environments that standardize on GHCR.
Continue reading “rqlite images now available on GitHub Container Registry”
My teams recently delivered support for the OpenTelemetry Protocol (OTLP) into Google Cloud Observability. This marks a significant step toward open, vendor-neutral observability.
By adopting OTLP, customers gain interoperability across tools, simpler data pipelines, and a future-proof path as the ecosystem standardizes. The change strengthens data quality in Cloud Trace today and sets the stage for metrics and logs to follow.
You can read the full announcement on the Google Cloud blog.
I was recently interviewed by Noah Brier for his BRXND Tokens & Tactics AI newsletter. Noah and I used to work together a few years ago at Percolate so it was good to connect again.
You can check out the interview here.
rqlite is a lightweight, user-friendly, open-source, distributed relational database. It’s written in Go, employs Raft for distributed consensus, and uses SQLite as its storage engine.
rqlite 9.0 introduces Change Data Capture (CDC), enabling you to stream the changes occurring to the underlying SQLite database to other systems. With CDC, rqlite is no longer just a distributed database—it’s a live event source. So let’s take a look at what the latest release allows us to do, and some of the design challenges that needed solving — especially building Change Data Capture on SQLite.
Continue reading “rqlite 9.0: Real-time Change Data Capture for Distributed SQLite”
rqlite is a lightweight, open-source, distributed relational database written in Go, which uses SQLite as its storage engine.
Development for the 9.0 release has started, and should be an important release. The main goals for 9.0 include:
Upgrading from the 8.x release series should be seamless.
Two years ago, I appeared on Contributor, a podcast hosted by Eric Anderson of Scale Venture Partners. I was there to talk about rqlite, the open-source database I maintain.
rqlite
is a lightweight, user-friendly, open-source, distributed relational database. It’s written in Go and uses SQLite as its storage engine.
When it comes to distributed systems the CAP theorem is an essential concept. It states that it’s impossible for a distributed database to simultaneously provide Consistency, Availability, and Partition tolerance. The challenge is in the face of a network partition, a database can only be available or consistent, but not both.
Let’s take a look at the CAP theorem and see how rqlite fits into this fundamental trade-off.
Continue reading “Consistency Over Availability: How rqlite handles the CAP Theorem”
rqlite is a lightweight, user-friendly, open-source, distributed relational database. It’s written in Go and uses SQLite as its storage engine. Recent versions—8.38.0 through 8.42.0—introduce several notable improvements, including Google Cloud Storage support, new HTTP APIs for cluster control, and improvements to Backup support.
Continue reading “rqlite 8.38.0 to 8.42.0: Leader Stepdown, Google Cloud Backups, and More”
rqlite is a lightweight, open-source, distributed relational database written in Go, utilizing SQLite as its storage engine.
Version 8.39 has been released and now includes support for automated backup and restore to and from Google Cloud Storage. This enhancement offers increased data protection and expands your Disaster Recovery options in case of emergencies.
We built the old software systems by hand. Line by line. Module by module. That era is ending.
Something profound is happening. For the first time in the history of software, we are not the only entities capable of understanding and generating code. And yet the role of the open-source developer has never mattered more.
This post is a statement of what we must preserve, what we must change, and how we must lead—now that we write software alongside intelligent systems.
Continue reading “The Developer’s Manifesto for the Age of LLMs”
rqlite is a lightweight, open-source, distributed relational database written in Go. It uses SQLite as its storage engine and Raft for consensus.
Last week, I wrote about my experience with language models, how they evolved from simple Python helpers to full-blown design partners and even a sort of AI Product Manager for rqlite, advising on features like Change-Data-Capture. I talked about assigning entire GitHub issues to agents, treating them like junior engineers who just wouldn’t quit until the PR was merged.
It was impressive, a fundamental shift in how I thought about shipping code. But that was last week. This week, the workflow has taken another, mind-blowing, leap.
Continue reading “GPT is writing the GitHub issues, Copilot is fixing them”
rqlite
is a lightweight, open-source, distributed relational database written in Go. It uses SQLite as its storage engine and Raft for consensus.
I’ve been developing rqlite for about ten years, and until recently, the workflow hadn’t changed much. I write the code. Others contribute here and there. GitHub issues are filed, triaged, and resolved. The usual.
Then language models showed up, and things started to shift.
rqlite is a lightweight, user-friendly, open-source, distributed relational database. It’s written in Go and uses SQLite as its storage engine.
Thanks to Jesus Zazueta there is a new JDBC driver for rqlite. Specifically it’s a Type 4 driver, which means it communicates directly with the rqlite node using its HTTP API.
Be sure to check out the repo on GitHub.
rqlite is a lightweight, open-source, distributed relational database written in Go, which uses SQLite as its storage engine and Raft for consensus.
Ten years ago, I tagged the first release of rqlite—a project I started to explore distributed consensus, to learn Go, and to build something useful. I had no roadmap, no plans for scale, and certainly no idea it would still be active a decade later.
Continue reading “rqlite turns 10: Observations from a decade building Distributed Systems”
