This article explains how to handle hundred‑thousand to million‑level QPS by using vertical and horizontal database sharding, detailing implementation steps, sharding algorithms, and the trade‑offs such as transaction complexity and distributed ID generation.
This article explains why database sharding is needed, how to identify performance bottlenecks, and provides step‑by‑step guidance on SQL tuning, table redesign, architectural changes, and practical horizontal and vertical sharding techniques with real‑world e‑commerce examples.
The article explains why relational databases become performance bottlenecks at large scales, introduces vertical and horizontal sharding techniques, discusses their advantages and drawbacks, and provides detailed guidance on handling distributed transactions, joins, pagination, global primary keys, and ID generation strategies.
This article explains why relational databases hit performance bottlenecks at large scale, introduces vertical and horizontal sharding techniques, compares their pros and cons, discusses common challenges such as distributed transactions, joins, pagination and global key generation, and offers practical solutions and middleware options.
Learn why large-scale internet applications need database sharding, understand the evolution from single databases to split databases and tables, and follow practical steps for assessing, planning, and implementing horizontal and vertical sharding, including sizing calculations, key selection, and query challenges.
This article explains the concepts, types, advantages, and challenges of database sharding—including vertical and horizontal partitioning—covers when to consider splitting, practical strategies for handling transactions, joins, pagination, global IDs, and lists popular middleware solutions for implementing sharding in production.
This article explains why and how to split databases and tables in high‑concurrency systems, covering vertical (business‑domain) and horizontal (data‑volume) sharding, practical architectures, read‑write separation, routing algorithms, and real‑world case studies from gaming, membership points, and restaurant ordering platforms.
The article examines why growing business complexity and throughput demands necessitate system decomposition and architectural evolution, detailing horizontal scaling, vertical and business splitting, database partitioning strategies, cache and index integration, remote service data sourcing, and asynchronous messaging to achieve scalable, robust micro‑service‑based solutions.
This article explains the concepts, types, advantages, and drawbacks of vertical and horizontal database sharding, discusses the challenges such as distributed transactions, cross‑node joins, pagination, global primary‑key generation, migration, and provides practical guidelines and case studies for deciding when and how to apply sharding.
This comprehensive guide explains why and when to split relational databases, details vertical and horizontal sharding techniques, discusses associated challenges such as distributed transactions, cross‑node joins, pagination, global primary keys, and offers practical solutions and middleware options.
The article explains why and when to apply database sharding, describes horizontal and vertical partitioning methods, lists common sharding tools, and discusses challenges such as distributed transactions, join avoidance, pagination, and global primary key generation.
This comprehensive guide explains the motivations, methods, and trade‑offs of database sharding—including vertical and horizontal partitioning, sharding rules, handling cross‑node joins, distributed transactions, global primary key generation, and practical migration strategies—so you can scale relational databases effectively.
The article explains how increasing business complexity and throughput demands drive system splitting—horizontal scaling, vertical and business sharding, and database partitioning—and describes the subsequent architectural evolution toward micro‑services, caching, indexing, and asynchronous processing to improve capacity, robustness, and performance.
This article explains MyCat's role as a database middleware, tracing the evolution from single‑database setups through distributed deployment, caching, master‑slave, vertical and horizontal sharding, and shows how MyCat automates data‑source and shard selection to reduce code complexity.
This article explores MySQL sharding fundamentals, detailing vertical, horizontal, and combined partitioning methods, their advantages and drawbacks, and surveys various open‑source implementations such as MySQL Proxy, HSCALE, Amoeba, HiveDB, and PL/Proxy, while offering practical guidance on configuration, transaction handling, and common pitfalls.
This article explains what MariaDB Spider is, its role as a pluggable storage engine for MySQL/MariaDB sharding, demonstrates vertical and horizontal partitioning with real‑world Tencent game case, provides installation steps, configuration commands, performance considerations, tunable parameters, and load‑balancing architecture.
The article examines the increasing storage bottleneck in large-scale web systems, explains vertical and horizontal database sharding, discusses the technical difficulties they introduce—including join rewrites, transaction handling, and ORM integration—and proposes practical approaches to minimize service impact and manage distributed transactions.
This article explains the core concepts of database sharding, detailing vertical and horizontal partitioning methods, strategies for combining them, handling shared data, and addressing challenges such as distributed transactions, cross‑node joins, and aggregation queries, with practical insights for scalable system design.
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.
Vertical sharding splits large tables across multiple servers by whole tables, offering simple partitioning but limited scalability, while horizontal sharding distributes rows of high‑traffic tables based on key rules, improving performance and scalability yet introducing complex partition logic and maintenance challenges.
