The article explains how exposing auto‑increment primary keys can leak business information, illustrates the danger with historical examples, and evaluates alternative ID generation strategies such as encoding, UUIDs, and Snowflake‑style distributed IDs, including performance comparisons in MySQL.
The article explains how InnoDB’s auto‑increment handling changed after MySQL 5.1.22—from using a table lock to a lightweight mutex for predictable‑row inserts—and details the three innodb_autoinc_lock_mode settings, their impact on concurrency and replication, and related pitfalls such as non‑sequential IDs.
This article details MySQL performance enhancements—including Group Commit redesign, DDL fast‑fail lock handling, GTID allocation refinements, persistent auto‑increment storage, and replication parallelism improvements—illustrating the underlying mechanisms, implementation steps, and benchmark results that demonstrate measurable throughput gains.
This article details MySQL performance enhancements covering Group Commit redesign, XA recovery handling, DDL fast‑fail implementation, GTID allocation optimizations, and a fix for InnoDB auto‑increment duplication, each supported by concrete test data and code changes.
This article explains MySQL's Group Commit mechanism, DDL fast‑fail enhancements, GTID allocation optimizations, fixes for InnoDB auto‑increment duplication after restart, and the evolution of replication performance from 5.5 to 5.7, including detailed code snippets and benchmark results.
