MySQL Concurrency: Locking and Transactions for MySQL Developers and DBAs

Concurrency Is Where MySQL Gets Interesting — and Difficult

MySQL Concurrency: Locking and Transactions for MySQL Developers and DBAs is a focused technical guide to the mechanisms that decide whether concurrent workloads flow smoothly or grind to a halt. Jesper Wisborg Krogh examines how MySQL and InnoDB coordinate simultaneous access to data, why locks and transactions sometimes collide, and how to investigate those collisions without guesswork.

Published by Apress in 2021, the book is aimed at readers who already work with MySQL and need a deeper operational understanding of concurrency, not a beginner’s introduction to SQL.

What the Book Covers 💻

The material moves from core concepts to diagnostic tools and then into detailed case studies. Early chapters establish the language of locks and transactions; later chapters turn to monitoring, isolation levels, indexes, foreign keys, and the behavior of InnoDB internals. Topics include:

• Lock access levels and high-level lock types
• InnoDB record locks, next-key locks, mutexes, and semaphores
• Monitoring locks, mutexes, and transactions through status counters, metrics, and Performance Schema
• Transaction isolation levels and their practical consequences
• Indexes and foreign keys as they relate to locking
• Techniques for reducing contention and resolving lock conflicts

Monitoring Before Troubleshooting ⚙️

A recurring strength of the book is its emphasis on observability. Rather than treating deadlocks and lock waits as mysterious events, it shows how MySQL exposes what is happening: InnoDB metrics, lock monitors, transaction tables, and Performance Schema instrumentation. That evidence-driven approach helps developers and DBAs form a factual picture before changing configuration or rewriting queries.

Case Studies from Real MySQL Behavior 🔍

The later chapters are built around case studies, including flush locks, metadata and schema locks, record-level locks, deadlocks, foreign keys, and semaphores. Each scenario gives readers a way to connect low-level concepts to the kinds of symptoms that show up in production: stalled queries, rising wait times, failed transactions, and sudden contention under load.

Who Will Get the Most from This Book 🧠

This is a natural fit for MySQL developers, database administrators, site reliability engineers, and backend engineers who support applications with meaningful write concurrency. It will be most useful to readers who are comfortable with SQL and MySQL basics and now want to understand what happens below the query text. The book’s structure also makes it a useful reference for teams investigating performance incidents or planning schema changes that affect locking.

Why It Remains Relevant

Concurrency issues are often intermittent, workload-dependent, and difficult to reproduce. MySQL Concurrency addresses that reality by combining mechanisms, monitoring, and case-based reasoning. For anyone responsible for keeping MySQL systems responsive under load, it offers a structured way to reason about locks and transactions instead of relying on trial and error.