Bigtable at Twenty: What Stayed and What Got Rebuilt
SIGMOD Companion '26 has a 13-page paper by 50+ Google authors revisiting Bigtable two decades on. 10 EB, 7 billion QPS, and an architecture that barely moved. This is my reading of why.
CEO & Founder of Greptime. Writing about systems, distributed computing, AI & Programming.
SIGMOD Companion '26 has a 13-page paper by 50+ Google authors revisiting Bigtable two decades on. 10 EB, 7 billion QPS, and an architecture that barely moved. This is my reading of why.
An idea someone had fully worked out back in 2018, yet it took eight years before it could actually be built. This piece is about one thing: why now.
When agents go to production, they break the four assumptions today's infrastructure was built on: deterministic, human-driven, request-response, stateless. A first-principles walk through what actually breaks.
A migration retro: forking Langfuse to swap its analytics store from ClickHouse to GreptimeDB, run mostly by two AI agents. Most of the work was paying down the debt of one decision — make a single database both the source of truth and the analytics layer.
Part 1 was about how the three pillars split apart. This part is about how many smart people, starting in 2018, tried to put them back together — what they actually built, and why none of it quite reached the finish line.
Today we treat metrics, logging, and tracing as the natural structure of observability. But it wasn't designed; it grew. Part 1, on how it split apart (2010–2017).
Datadog's Investor Day deck quietly redefines observability: the object of observation turns probabilistic, AI agents become operators, and the reader of the data shifts from human to model.
TMA1 v2 adds an MCP server, enhanced hooks that auto-inject build/session/anomaly context, and cross-agent context sharing between Claude Code and Codex.
TMA1: a local observability tool for AI coding agents with full session trace, tool decision breakdown, latency tracking, and SQL-queryable storage.
Have we been building infrastructure for humans this whole time, without ever treating agents as users? Six principles for agent-friendly infrastructure, rooted in Unix philosophy.
My colleague called Database MCP 'pulling your pants down to fart.' After thinking about it, I mostly agree—but we built one anyway.
AI Coding doesn't fundamentally make you a better programmer. It's an amplifier—amplifying your strengths and your weaknesses.
The difference between using AI as a tool you pick up occasionally versus treating AI as infrastructure you don't know how to work without.
When AI can rewrite an entire module in seconds, do the design principles built for 'humans maintaining code' still apply?
AI's real value isn't in producing the final output—it's in creating Builders. Whether you can create Builders is what separates the 2x from the 100x.