Skip to main content
cd ../lexicon
sys/docs/lexicon/mysql.md
Lexicon
MySQL

MySQL

MySQL is a relational database management system that stores data in tables and is queried with SQL. Operationally, behaviour such as storage engines, replication and permissions varies by version, so confirm specifics in the official documentation before changing anything.
Difficulty: Introductory
3 min read
Updated 2026-11-08

In plain English

Plain definition

MySQL is a relational database management system that stores data in tables and is queried with SQL. Operationally, behaviour such as storage engines, replication and permissions varies by version, so confirm specifics in the official documentation before changing anything.

Technical definition

MySQL is a relational database management system (RDBMS). A server process accepts client connections, authenticates them, parses SQL statements, plans and executes them, and stores data through a storage engine layer. The documentation describes a pluggable storage engine architecture; which engines and features are available depends on the version and distribution, so confirm them in the MySQL documentation.

Operational relevance

Operators care about a small set of concerns: availability, data durability, access control, performance and recoverability. Typical activities include managing accounts and privileges, observing slow or blocked queries, planning backups and testing restores, and configuring replication where the version supports it. Any change should first be tried in an isolated, non-production environment, after confirming the product version and the permissions held.

Architecture relationship

MySQL usually sits in the data tier behind an application or service layer. Clients connect over a network or local socket, so network exposure, authentication and least-privilege accounts form part of its security boundary. Because it holds persistent state, it is also the component whose backup and recovery design most affects the recovery of the whole system.

Example

An application stores customer orders in an orders table. It runs a query such as SELECT id, status FROM orders WHERE id = 42. The server checks that the connecting account has read permission on that table, executes the query and returns one row. Observable success is that the expected row comes back under a read-only account, and that the same account is refused when it attempts to change data.

Misunderstanding

MySQL is not a backup. Replication copies changes, including mistaken ones, so it does not replace tested backups. Nor is MySQL a single fixed product: features and defaults differ between versions and distributions, so claims about behaviour should be checked against the documentation for the version in use.

  • SQL: the language used to query and change data.
  • RDBMS: the general class of system MySQL belongs to.
  • Storage engine: the component that stores and retrieves table data.
  • Replication: copying changes from one server to another.

Further reading

Start with the official MySQL documentation and select the manual for the version you run. Before any change, confirm the version and your permissions, rehearse in a non-production environment, take a verified backup so you can roll back, and proceed only when you can state what success looks like. If you cannot, escalate to a database owner.

About this page

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.