Adding a new column to a core MySQL order table with tens of millions of rows can lock the table and disrupt services, so this article explores safe alternatives such as master‑slave switching, online schema change tools, extension tables, JSON fields, and clever reuse of existing redundant columns.
This guide explains why using a plain ALTER TABLE on massive MySQL tables can lock the table and halt services, and presents tool‑based online DDL, native INPLACE options, phased migration strategies, cloud‑DB features, best‑practice checks, monitoring, and rollback techniques to add new columns safely.
When a new business field is required on a core order table with tens of millions of rows, the article walks through the risks of direct ALTER TABLE, evaluates master‑slave switching, online DDL tools, extension tables, JSON‑based schema‑less designs, and a clever reuse of an existing redundant column, providing practical steps and performance insights.
Adding a new field to a core order table with tens of millions of rows can lock the table and disrupt services, so this article explores various strategies—including master‑slave switching, online DDL tools, extension tables, JSON fields, and repurposing redundant columns—to achieve schema changes safely and efficiently.
JD Advertising built a massive ad‑data warehouse on Apache Doris, reaching nearly 1 PB and 18 trillion rows, then implemented a hot‑cold data tiering strategy—first a lake‑based approach, later a native tiering solution in Doris 2.0—reducing storage costs by 87% and boosting query performance over tenfold.
This article details JD Advertising's journey from a 1 PB Apache Doris data lake to a multi‑level hot‑cold tiering architecture, describing two tiering strategies, the performance and schema‑change challenges faced during the upgrade to Doris 2.0, and the optimizations that reduced storage costs by about 87% while boosting query throughput.
JD Advertising built a petabyte‑scale ad analytics service on Apache Doris, identified a hot‑cold access pattern, and implemented a native cold‑hot tiering solution (upgrading to Doris 2.0 and optimizing schema changes) that cut storage costs by ~87% and boosted concurrent query capacity over tenfold while simplifying operations.
This article presents JD Advertising's engineering experience with Apache Doris, describing the evolution from a data‑lake cold‑data solution to a native cold‑hot tiering approach, detailing performance regressions after upgrading to Doris 2.0, and outlining a series of optimizations for query speed, CPU and memory usage, schema‑change efficiency, and automated data migration and restoration.
This article recounts the development of ZzoOnlineDDL, a MySQL schema‑change platform, detailing its 1.0 limitations, the 2.0 architectural upgrades, feature set—including intelligent tool selection, timed execution, sharding support, monitoring, and retry mechanisms—and lessons learned from real‑world incidents such as MDL locks, disk pressure, and unique‑index pitfalls.
This article details a step‑by‑step strategy for expanding a VARCHAR column from 50 to 500 characters on a 4‑hundred‑million‑row MySQL 8.0 table, evaluating online DDL, gh‑ost, pt‑osc, and ultimately implementing a cascade replication workflow to meet a four‑hour downtime window.
This article explains ByteKV's design—using range partitioning, a custom Raft implementation, multi‑layer architecture, and advanced load‑balancing strategies—to provide strong consistency, flexible data models, and seamless scalability for large‑scale storage workloads.
This article provides a comprehensive guide to gh-ost, the GitHub‑released online MySQL schema migration tool, covering its design principles, three migration modes, download and RPM installation, common command‑line options, interactive socket commands, and a step‑by‑step example of altering a column type while monitoring progress and performing a safe cut‑over.
This article explains how MySQL performs DDL operations on large tables without long‑lasting locks, covering the evolution from copy‑table and in‑place methods to Fast Index Creation, Online DDL introduced in 5.6, and third‑party tools PT‑OSC and GH‑OST, with detailed process steps and comparisons.
This article explains the challenges of MySQL DDL on large tables, details the built‑in COPY, INPLACE, and INSTANT algorithms, compares third‑party tools like pt‑online‑schema‑change and gh‑ost, and provides practical guidance on minimizing impact, monitoring progress, and handling metadata locks.
This article explains how to perform zero‑downtime deployments by handling database schema incompatibilities, covering both non‑backward‑compatible and backward‑compatible migration strategies, using Flyway with Spring Boot, and providing step‑by‑step guidance, code examples, A/B testing, and rollback procedures.
