https://www.youngju.dev/blog 천천히 올바르게. AI Researcher & DevOps Engineer Youngju's tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering. ko fjvbn2003@gmail.com (Youngju Kim) fjvbn2003@gmail.com (Youngju Kim) Fri, 15 May 2026 00:00:00 GMT https://www.youngju.dev/blog/culture/2026-05-15-distributed-sql-newsql-2026-cockroachdb-tidb-yugabytedb-spanner-aurora-dsql-neon-deep-dive.en https://www.youngju.dev/blog/culture/2026-05-15-distributed-sql-newsql-2026-cockroachdb-tidb-yugabytedb-spanner-aurora-dsql-neon-deep-dive.en 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 word HTAP down to production reality, and YugabyteDB has cemented its Postgres-compatible distributed lane. Google Spanner has kept its external-consistency throne while polishing the PostgreSQL interface, and Aurora DSQL has become the default distributed SQL inside AWS since its December 2024 GA. AlloyDB and Citus scale Postgres within a single region, Vitess and PlanetScale have diverged on the long road of MySQL sharding, and Neon — even after the Databricks acquisition — still claims the serverless Postgres throne. This piece compares twelve systems through the lens of consensus algorithms, MVCC, hybrid logical clocks, geo-replication, and online schema change, then ends with concrete picks for the four real use cases: global SaaS, multi-tenant, HTAP, and serverless. Fri, 15 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) databasedistributed-sqlnewsqlcockroachdbtidbyugabytedbspanneraurora-dsqlalloydbcitusvitessplanetscaleneonxatapostgres2026deep-diveenglish https://www.youngju.dev/blog/culture/2026-05-15-distributed-sql-newsql-2026-cockroachdb-tidb-yugabytedb-spanner-aurora-dsql-neon-deep-dive.ja https://www.youngju.dev/blog/culture/2026-05-15-distributed-sql-newsql-2026-cockroachdb-tidb-yugabytedb-spanner-aurora-dsql-neon-deep-dive.ja 2026年の分散SQLの地形は、2020年代初頭の「NewSQL」という一語ではもう括れなくなった。CockroachDB 24はライセンス変更から1年半を経て自分の場所を見つけ、TiDB 8はHTAPという単語を本番に引きずり下ろし、YugabyteDBはPostgres互換分散という路線を固めた。Google Spannerは外部一貫性という本丸を守りながらPostgreSQLインターフェースを磨き、Aurora DSQLは2024年12月のGA以降、AWS陣営のデフォルト分散SQLになった。AlloyDBとCitusはシングルリージョン内でPostgresを伸ばし、VitessとPlanetScaleはMySQLシャーディングという長い道で分岐し、NeonはDatabricks買収後もサーバレスPostgresの標準を自任する。本稿は12のシステムを合意アルゴリズム・MVCC・HLC・地理レプリケーション・オンラインスキーマ変更という共通語彙で一気に比較し、「グローバル / SaaSマルチテナント / HTAP / サーバレス」という4つの用途で誰を選ぶべきかまで踏み込む。 Fri, 15 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) databasedistributed-sqlnewsqlcockroachdbtidbyugabytedbspanneraurora-dsqlalloydbcitusvitessplanetscaleneonxatapostgres2026deep-dive日本語 https://www.youngju.dev/blog/culture/2026-05-15-distributed-sql-newsql-2026-cockroachdb-tidb-yugabytedb-spanner-aurora-dsql-neon-deep-dive https://www.youngju.dev/blog/culture/2026-05-15-distributed-sql-newsql-2026-cockroachdb-tidb-yugabytedb-spanner-aurora-dsql-neon-deep-dive 2026년의 분산 SQL 지형은 2020년대 초의 "NewSQL"이라는 단어로 더 이상 묶이지 않는다. CockroachDB 24는 라이선스 변경 1년 반을 지나며 자기 자리를 찾았고, TiDB 8은 HTAP라는 단어를 실전으로 끌어내렸으며, YugabyteDB는 Postgres 호환 분산이라는 노선을 굳혔다. Google Spanner는 외부 일관성이라는 본진을 지킨 채 PostgreSQL 인터페이스를 더 매끄럽게 다듬었고, Aurora DSQL은 2024년 12월 GA 이후 AWS 진영의 디폴트 분산 SQL이 되었다. AlloyDB와 Citus는 단일 리전 안에서 Postgres를 확장하고, Vitess와 PlanetScale은 MySQL 샤딩이라는 오랜 길에서 갈라졌으며, Neon은 Databricks 인수 이후에도 Postgres 서버리스의 표준을 자처한다. 이 글은 12개의 시스템을 합의 알고리즘·MVCC·HLC·지오 복제·온라인 스키마 변경의 관점에서 한 번에 비교하고, "글로벌 / SaaS 멀티테넌트 / HTAP / 서버리스"라는 네 가지 사용처에서 누가 무엇을 골라야 하는지까지 적는다. Fri, 15 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) databasedistributed-sqlnewsqlcockroachdbtidbyugabytedbspanneraurora-dsqlalloydbcitusvitessplanetscaleneonxatapostgres2026deep-dive