- Published on
All Posts
All Posts
- database (12)
- distributed-system (7)
- paper-reading (4)
- proxy (3)
- mysql (3)
- kubernetes (2)
- operator (2)
- code-for-fun (2)
- life (2)
- daily (2)
- transaction (2)
- lock (2)
- ddl (2)
- wescale (2)
- career (1)
- travel (1)
- testing (1)
- vectorization (1)
- performance-test (1)
- onlineddl (1)
- connection-pool (1)
- serverless (1)
- s3 (1)
- github-actions (1)
- tunnel (1)
- tls (1)
- Published on
This article explains the challenges of scaling database connections and how connection pooling and multiplexing can address them.- Published on
This article explains and compares the CutOver algorithms of pt-osc, gh-ost, and Facebook's OnlineSchemaChange.- Published on
Exploring the design of a distributed read-write lock for PolarDB-X, this blog delves into the complexities and considerations of ensuring synchronized DDL execution in a distributed database environment.- Published on
Detailed explanation of how to write a Kubernetes operator by building a TicTacToe game.- Published on
I am learning kubernetes, so I write a TicTacToe game based on Kubernetes Operator. This is a sample project to demonstrate how to build a Kubernetes Operator with Kubebuilder.- Published on
This article compares WeScale, a MySQL-compatible database proxy, with MySQL, highlighting its read-write splitting, connection pooling, and failover features. WeScale maintains high throughput and low latency under heavy loads, with minimal additional memory use and about 1/3 CPU overhead. It scales better both horizontally and cost-effectively than scaling MySQL vertically.- Published on
The article explains WeSQL WeScale's read-write splitting, ensuring read-after-write consistency and load balancing.- Published on
The article discusses the necessity of ACID properties for database DDL operations, challenges in traditional systems, and how PolarDB-X implements transactional DDL, ensuring atomicity, consistency, isolation, and durability to enhance reliability and operational flexibility.- Published on
Database schema evolution (DDL) poses unique challenges in ensuring concurrency with transactions while maintaining ACID properties. Traditional approaches use metadata locks (MDLs) to serialize DDL and DML/DQL, but this can severely impact performance. This blog discusses the issues and explores solutions like multi-version concurrency control to enable highly concurrent non-blocking schema changes.