A MySQL‑based receipt‑tracking service suffered a sudden 100‑fold load increase, prompting a step‑by‑step optimization that combined read‑write splitting, middleware‑less data routing, columnar storage with Infobright, and dynamic scheduling to dramatically lower CPU/IO pressure and restore performance.
The article explains how high‑concurrency systems can be built by decomposing workloads through optimistic locking, read‑write database splitting, resource separation with CDN acceleration, dynamic‑to‑static conversion, caching, and load‑balancing strategies, providing practical code examples for each technique.
The article outlines how a Discuz website’s MySQL infrastructure progresses through five stages—from a single‑machine setup for low traffic to multi‑master, read‑write split, and finally sharding and partitioning—to handle daily page views growing from under ten thousand to ten million.
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 explains the concept of read/write splitting in distributed databases, outlines two implementation methods—static dual data sources and dynamic AOP-based switching—provides a complete Spring‑MyBatis demo with configuration files, code snippets, and guidance on setting up master and slave connections.
This tutorial walks through setting up a Mycat environment, creating required databases and users, installing JDK7 and Mycat, configuring environment variables and MySQL settings, defining sharding rules, and verifying both read/write separation and automatic failover in a master‑slave MySQL cluster.
This guide walks through setting up a MySQL master‑slave cluster, installing MaxScale, configuring authentication, monitoring, routing and logging plugins, testing read/write split and load balancing, and handling single‑ or multiple‑slave failures with automatic failover.
This guide explains what MaxScale is, its plugin architecture, and provides step‑by‑step instructions to install, configure, start, and test MaxScale for MySQL read/write splitting and load balancing in a master‑slave cluster.
Learn the fundamentals of MySQL read/write splitting, why it boosts performance, and step‑by‑step instructions to configure master‑slave replication, create users, set up MySQLProxy, and verify the split‑read behavior using command‑line examples on a test environment.
This article explains how large‑scale internet applications can overcome database bottlenecks by using load‑balancing clusters, implementing read/write separation, and applying vertical or horizontal sharding, while outlining each method's principles, implementation steps, advantages, and drawbacks.
The article explains that 503 errors under high concurrency are usually caused by database bottlenecks and outlines a systematic approach—including read‑write separation, caching with memcached, consistent hashing, vertical partitioning, and horizontal sharding—to improve website scalability and reliability.
This article explains MySQL replication fundamentals, detailing master‑slave and multi‑master architectures, thread roles, configuration parameters, read‑write splitting, multi‑source setups, and advanced scenarios such as multi‑level and circular replication, while highlighting common pitfalls and performance considerations.
To ensure 24/7 availability for e‑commerce and gaming platforms, this article examines MySQL architecture from business analysis to common patterns, including read‑write ratios, consistency models, sharding strategies, historical data migration, and cluster scaling, highlighting practical designs for disaster‑tolerant, high‑performance systems.
This article explains MySQL architecture design for 24/7 online services, covering business analysis of read‑write patterns, common deployment models, consistency levels, data migration, sharding strategies (vertical, horizontal, and business‑level), and cluster scaling for high availability.
Amoeba is an open‑source MySQL front‑end proxy that acts as an SQL router, offering load balancing, high availability, query filtering, read/write splitting, and linear scaling, thereby simplifying data sharding, reducing client connections, and enabling seamless database expansion.
