This article presents a comprehensive migration plan for a legacy MongoDB‑based system, detailing scope analysis, dual‑write implementation, data source selection, bulk and incremental migration strategies, and a three‑pronged online approach (monitoring, gray release, rollback) to ensure a smooth cut‑over without service disruption.
This article presents two practical database migration schemes—dual‑write and a gray‑scale switch—detailing their workflows, code refactoring, data synchronization using Syncer, consistency verification with sync‑diff‑inspector, and operational trade‑offs for minimizing downtime and ensuring data integrity.
This article explains common business scenarios such as large‑table splitting, cross‑database migration, and data synchronization, then compares loss‑bearing and loss‑less migration strategies, and provides detailed step‑by‑step implementation guidance for smooth dual‑write migration and real‑world tooling.
This technical guide explains how to scale a sharded database horizontally by introducing five expansion schemes—including shutdown, write‑stop, log‑based, dual‑write, and smooth 2N approaches—covers MariaDB installation, master‑master replication setup, dynamic data‑source configuration with ShardingJDBC, and detailed Keepalived high‑availability configuration for seamless service continuity.
The article details how a rapidly growing airline ticket order system was re‑architected by identifying performance bottlenecks, applying vertical and horizontal sharding, optimizing cache layers, implementing dual‑write mechanisms, and planning a phased migration to achieve ten‑fold QPS growth while reducing resource usage and operational risk.
This article explains why dual‑write consistency between MongoDB and a relational database is challenging, compares common misconceptions with cache usage, and provides practical patterns—including write ordering, retry mechanisms, and scheduled cleanup—to reliably synchronize core and non‑core data.
This article explores common misconceptions and practical strategies—including write ordering, delayed double‑delete, retry mechanisms, and scheduled cleanup jobs—to ensure reliable dual‑write consistency between MongoDB and traditional relational databases.
This article details Ctrip's comprehensive redesign of its airline ticket order database, covering the background performance bottlenecks, vertical and hot‑cold data splitting, sharding key selection, multi‑level caching, cross‑shard query optimization, dual‑write mechanisms, fault‑tolerance strategies, project planning, and the resulting improvements in scalability and cost.
This article outlines the background, analysis, design, testing strategy, migration plan, and production quality results for implementing horizontal sharding, table splitting, and Elasticsearch integration in a growing enterprise database system.
This article outlines a comprehensive, step‑by‑step approach for migrating massive tables—up to billions of rows—through sharding, dual‑write, data synchronization, validation, testing, and controlled switch‑over to ensure minimal impact on production services.
This article details how JD Daojia's order center migrated from a simple MySQL‑backed system to a high‑throughput Elasticsearch cluster, describing each architectural phase, performance tuning measures, dual‑cluster real‑time backup, version upgrades, data synchronization strategies, and the key pitfalls encountered such as deep pagination and FieldData memory issues.
Alibaba migrated Xianyu Coin’s points from the legacy KingTower platform to the new Banliang service using a four‑phase, service‑based approach—preparation, active/passive data migration with distributed locks, dual‑write for consistency, reconciliation, and a gradual service switch—completing the transition in a month without user impact.
