This article examines how Yirendai tackled the high‑concurrency, big‑data challenges of internet finance by evolving its architecture through four major versions, introducing performance optimizations, service decomposition, database scaling, and cloud‑native strategies to support massive user growth while preserving a seamless customer experience.
This article explains the architecture and key features of CDB for MySQL read-only instances and RO groups, including read-write separation, horizontal scaling, automatic load balancing, health checks, and dynamic instance removal for high-delay instances.
Database sharding, or splitting databases into multiple instances and tables, is essential for scaling backend systems; this article explains its importance, historical context, core concepts, storage stretching techniques, index and consistency handling, and provides a practical design example for transaction systems.
This article details JD.com’s comprehensive strategies—including architecture design, pre‑event preparation, real‑time safeguards, and post‑event analysis—to ensure MySQL databases remain high‑performance and highly available during massive traffic spikes like 618 and Double‑11 sales.
This article explains how website systems achieve scalability through architectural designs such as physical function separation, server clustering, various load‑balancing techniques, distributed cache mechanisms, and both relational and NoSQL database scaling methods, providing practical guidance for large‑scale web deployments.
Server Clusteringbackend architecturedatabase scaling
This article presents a comprehensive guide to database sharding, covering implementation strategies, vertical and horizontal partitioning, global primary key generation techniques, framework versus custom solutions, multi‑data‑source transaction handling, and a novel, migration‑free scaling approach that combines incremental range and hash‑based routing.
This article analyzes the business flow, technical challenges, and architectural design of a flash‑sale (seckill) system, offering practical solutions for isolation, high‑concurrency handling, database sharding, caching, cheating prevention, and data consistency to ensure reliable high‑traffic e‑commerce operations.
This article explains how to scale MySQL for large‑scale, high‑concurrency applications by using business splitting, master‑slave replication, database sharding and partitioning, and provides practical implementation strategies, code examples, and references to useful tools and middleware.
This article outlines the challenges of high‑traffic scenarios such as flash sales and timed red‑packet distribution, and presents a comprehensive backend architecture—including load balancing, database clustering, NoSQL caching, CDN, concurrency testing, message queues, first‑level caching, and static data strategies—to ensure smooth operation and optimal user experience.
This article explains practical sharding implementation strategies, global primary‑key generation techniques, framework versus custom solutions, distributed transaction models, and a flexible expansion scheme that avoids data migration while maintaining performance and scalability.
This article presents a comprehensive, practice‑driven analysis of horizontal database sharding for a high‑traffic e‑commerce order system, covering sharding dimensions, strategies, quantity planning, transparent routing, pagination challenges, lookup mapping, overall architecture, deployment steps, and the measurable performance and cost benefits achieved.
This article explains the three scenarios that trigger MongoDB chunk migration, describes the Balancer's lock‑based operation, and walks through the six detailed steps—including tag‑based splits, draining shard handling, and load‑balancing thresholds—that ensure data is evenly distributed across shards.
This article reviews Redis's native limitations, explains three clustering approaches—client‑side sharding, proxy sharding (e.g., Twemproxy), and the official Redis Cluster—then compares Twemproxy's drawbacks and introduces Codis as a modern, open‑source alternative with practical deployment tips.
The article explains when MySQL sharding is needed, outlines five practical principles for deciding to split databases or tables, provides real‑world examples, and shares operational tips for implementing horizontal partitioning to improve performance, availability, and manageability.
This article uses the Golden Circle framework to explore MySQL replication, detailing its definition, benefits such as scaling and fault tolerance, the underlying mechanisms involving binary logs and IO/SQL threads, and addressing common practical questions through a self‑Q&A format.
The article compares relational databases like MySQL—highlighting their consistency, transaction support, and join capabilities—with NoSQL alternatives, explaining each type’s strengths and limitations in handling massive writes, schema changes, variable fields, and simple queries, and guides developers on when to choose each.
The article presents the Binlog Server, a component that replaces intermediate masters in MySQL replication topologies to reduce network saturation, simplify disaster recovery, and improve high‑availability while supporting large numbers of slaves across remote sites.
The article reviews the evolution of large‑scale website architecture, explaining how business complexity, multi‑server deployment, session handling, load balancing, database read/write separation, caching, and search indexing together address availability, concurrency, and performance challenges in modern web systems.
This article compiles Russell Smith’s comprehensive MongoDB best‑practice guide, covering architecture choices, file limits, write safety, schema design, replication, sharding, security, and performance tuning to help engineers avoid common pitfalls and optimize production deployments.
This article explains the concept, benefits, methods, and practical considerations of partitioning data across multiple Redis instances, covering range and hash partitioning, consistent hashing, implementation options, drawbacks, and recommended tools such as Redis Cluster and Twemproxy.
Airbnb tackled rapid data growth by vertically partitioning tables across multiple MySQL databases using Amazon RDS replication, minimizing downtime through read‑replica promotion, and implementing a staged migration that reduced primary database writes by 33%, cut size by 20%, and improved stability and scalability.
When read traffic overwhelms a single MySQL master, cascading replication and dual-master setups can distribute slave load, reduce replication lag, and simplify failover, offering a scalable solution that balances read/write pressure across multiple replication layers.
This article presents 58.com’s experience with MySQL under massive data volumes, covering core concepts such as single‑instance, sharding, replication and grouping, common availability and read‑write challenges, detailed sharding implementations for user, post, friend and order tables, and post‑sharding business practices including IN queries, non‑partition key queries, and cross‑database pagination.
This article explains the four‑step online data migration process—including dual‑write, historical data transfer, read cut‑over, and cleanup—using a real‑world MySQL‑to‑HBase fan‑list case study, and provides practical tips for ensuring zero‑downtime and high data consistency.
In this interview, Liu Qiuqi shares his journey from a DBA at Sogou to Architecture Operations Director at BabyTree, revealing how MySQL powers massive e‑commerce and community sites, the high‑availability designs, storage strategies, and performance tuning techniques that keep services running smoothly.