0 views collected around this technical thread.
This article explains the fundamentals of database sharding and partitioning, why they are needed for massive data volumes, various vertical and horizontal splitting strategies, routing algorithms, client vs. proxy deployment models, and the practical challenges and solutions when using ShardingSphere 5.x.
Database sharding and table partitioning are essential scaling techniques that separate data across multiple databases and tables to handle growing user volume, data size, and concurrency, with explanations of when to split, methods (horizontal vs vertical), and a comparison of popular middleware solutions.
This article explains why high‑concurrency big‑data systems need database sharding, describes table‑level partitioning methods (modulus and range), shows how to implement them with MySQL and Java code, compares vertical and horizontal database splitting, and evaluates middleware solutions such as Sharding‑JDBC and Mycat.
This article explains the concepts, methods, advantages, and drawbacks of database sharding, covering vertical and horizontal partitioning, sharding rules, global primary key generation, distributed transaction issues, cross‑node queries, pagination, data migration, and practical case studies, with code examples and diagrams.
This article explains vertical and horizontal database sharding, compares hash‑modulo and range‑based partitioning schemes, and discusses their advantages, drawbacks, and the impact on scaling and hotspot problems in large‑scale applications.
This article explains how a high‑traffic messaging platform with tens of millions of users and billions of daily records can be optimized using MySQL partitioning, sharding (both client‑side and proxy‑side), vertical database splitting, and practical migration scripts to maintain performance and availability.
The article explains how increasing business complexity and throughput require system splitting, decoupling, and architectural evolution—covering horizontal and vertical scaling, database sharding, caching, and micro‑service patterns—to improve capacity, robustness, and performance of large‑scale applications.
The article reviews how increasing business complexity and throughput demands drive the need to split applications and databases, adopt horizontal and vertical scaling, implement business and service-level partitioning, and evolve system architecture toward micro‑services, caching, and asynchronous processing.
The article examines how the rapid growth of mobile and aggregated payments strains traditional IOE‑based payment systems, and outlines a comprehensive distributed transformation strategy that includes vertical service‑oriented splitting, horizontal sharding by data type, and practical approaches to handling distributed transactions, cross‑shard queries, scaling, disaster recovery, and operational monitoring.
The article explains the concepts of vertical and horizontal database splitting, compares their technical difficulties, discusses the impact on joins and transactions, and proposes practical approaches such as careful SQL refactoring, ORM decoupling, and selective use of distributed‑transaction techniques to maintain system stability and scalability.