This article explains how Vitess was created to overcome MySQL leader‑follower replication limits at YouTube, detailing its sidecar VTTablet, stateless VTGate router, topology key‑value store, and scaling strategies that enable billions of users to be served reliably.
The article explains Vitess's approach to generating globally unique identifiers by using dedicated sequence tables, details the underlying MySQL schema and Go implementation, and compares it with VtDriver's CAS‑based method, highlighting trade‑offs between transaction locks and lock‑free updates.
This article examines YouTube's massive backend infrastructure, detailing its use of MySQL with Vitess for horizontal scaling, caching with Memcache, coordination via Zookeeper, cloud‑native deployment on Kubernetes, CDN delivery, and the storage systems (GFS, BigTable) that enable billions of users to upload and stream petabytes of video data.
This article explores how YouTube handles massive video uploads and billions of daily views by detailing its backend micro‑services, MySQL‑based Vitess clustering, sharding, replication, disaster recovery, cloud‑native deployment, CDN strategy, and large‑scale storage architecture.
This article explores how YouTube handles massive video uploads and billions of daily views by employing a sophisticated backend stack—including MySQL clusters powered by Vitess, sharding, replication, caching, disaster recovery, and cloud‑native deployment on Kubernetes—ensuring scalability, reliability, and low‑latency delivery.
This article examines YouTube’s massive backend infrastructure, detailing how the platform stores billions of videos using MySQL, Vitess for horizontal scaling, sharding, replication, disaster management, cloud‑native deployment on Kubernetes, and the supporting storage systems such as GFS and BigTable.
Vitess 12, the latest major release of the MySQL clustering solution, introduces the experimental Gen4 query planner, enhanced VTAdmin multi‑cluster management, role‑based access control, updated benchmarking tools, and more inclusive naming conventions to improve scalability and cloud deployment.
This article introduces Vitess, a cloud‑native MySQL sharding middleware, explains its key features, architecture, core concepts such as cells, keyspaces, shards and vindexes, and provides a step‑by‑step guide to performing a reshard from two to four shards while highlighting operational challenges and practical recommendations.
This article explains the fundamentals of database transactions, introduces Vitess's architecture, and details how Vitess implements a two‑phase commit protocol for distributed transactions, including transaction IDs, metadata management, preparation, commit, rollback, error handling, and performance considerations, with illustrative Go code snippets.
This article explains Vitess’s two‑phase commit mechanism for distributed transactions, covering the ACID properties, shard architecture, transaction manager roles, detailed code flow, metadata handling, preparation, commit, rollback, and various failure scenarios, along with practical examples and performance considerations.
