Tag Archives: design

9 years of open-source database development

rqlite is a lightweight, open-source, distributed relational database written in Go, which uses SQLite as its storage engine.

I’ve been developing rqlite since 2014 and its design and implementation has evolved substantially during that time — and the design docs tell the story of what worked, and what didn’t. So what can we learn about distributed database design, from watching rqlite change over the years?

Continue reading 9 years of open-source database development

rqlite 7.0: Designing Node Discovery and Automatic Clustering

rqlite is a lightweight, open-source, distributed relational database written in Go, which uses SQLite as its storage engine and Raft for distributed consensus. Release 7.0 is out now and introduces the first wave of new Node Discovery and Automatic Clustering  features.

Continue reading rqlite 7.0: Designing Node Discovery and Automatic Clustering

Logs and Time Series are not the same

When it comes to logs and time series, there is no magicIf you work in the logging, monitoring — or even Observability — space long enough, you eventually end up on team that tries to build a system that handles both logs and time series in a high-performant and cost-efficient manner.

Well, it’s a lot harder than it sounds — because logs and time-series are not the same.

Continue reading Logs and Time Series are not the same

Why Slack isn’t working

Slack: Where work happens

Something is happening at companies that use Slack. Slack, the company, may claim it’s work, but it’s less and less productive work, and it’s having a destructive affect upon my own field of software development.

I like really Slack, Flowdock, Hipchat and their ilk — I’ve written about it before. I couldn’t do my job without them. But it’s time to confront the damage these tools are causing.

Continue reading Why Slack isn’t working