Tag: #tidb
Writing on GPUs, LLMs, MLOps, Kubernetes — and mindset · 4 posts
Database Engines 2026 Deep-Dive — Postgres Won the API, ClickHouse and DuckDB Won Analytics
PostgreSQL 17/18, MySQL 9, MariaDB 12, SQLite + libSQL + Turso, DuckDB 1.x, ClickHouse, StarRocks, Doris, Druid, Pinot, TiDB, CockroachDB 25, YugabyteDB, Cassandra 5, ScyllaDB, Aerospike, Neon, Supabase, PlanetScale, Xat
2026-05-16 · 17 min read #database#postgresql#mysql#clickhouse#duckdbDistributed SQL / NewSQL 2026 — CockroachDB / TiDB / YugabyteDB / Spanner / Aurora DSQL / Neon Deep Dive
The 2026 distributed SQL landscape no longer fits under the single word "NewSQL" that defined the early 2020s. CockroachDB 24 has settled into its position eighteen months after its license change, TiDB 8 has dragged the
2026-05-15 · 18 min read #database#distributed-sql#newsql#cockroachdb#tidbRaft Consensus Complete Guide 2025: Leader Election, Log Replication, Safety, etcd/Consul in Practice
etcd, Consul, CockroachDB, and TiDB all use Raft because it is understandable. Leader Election, Log Replication, Safety Properties, Membership Change, and Snapshots — a deep dive with real-world system analysis.
2026-04-15 · 10 min read #raft#consensus#distributed-systems#leader-election#log-replicationDistributed Databases 2025 — CockroachDB, Spanner, TiDB, Yugabyte, Aurora DSQL, Neon, PlanetScale, Turso, D1 (S7 E3)
The "just use one database" era is over. In 2024–2025 distributed SQL (CockroachDB, Spanner, TiDB, Yugabyte), serverless Postgres (Neon, Supabase, PlanetScale, Aurora DSQL), and edge SQLite (Turso/libSQL, Cloudflare D1)
2026-04-15 · 11 min read #database#distributed-sql#postgresql#cockroachdb#spanner