What Is MySQL?

What Is MySQL?

MySQL is a relational database management system (RDBMS) that stores data in tables made of rows and columns. It uses the standard SQL (Structured Query Language) to access and modify that data. It runs on a client-server model: a server process manages the data, while applications connect to it over the network and send queries.

The project was originally developed by the Swedish company MySQL AB. Over the years it passed to Sun Microsystems and then to Oracle Corporation. Today MySQL is distributed both as an open-source Community edition and in commercial editions offered by Oracle.

A Brief History

MySQL's history goes back to the mid-1990s. Open-source licensing helped it attract a broad community, and it became a core component of the LAMP stack (Linux, Apache, MySQL, PHP/Perl/Python). That stack was the de facto standard powering much of the early web and played a decisive role in MySQL's rise.

Over time, MySQL found use across a wide range of systems, from simple content sites to large-scale platforms. Its low barrier to entry, abundant learning resources, and mature drivers for nearly every programming language made it a familiar choice for developers.

After Oracle took over MySQL, part of the original team who wanted the project to remain free started a fork. That fork lives on today as a separate project, MariaDB. While the two remain largely compatible, they have diverged over time at the feature, storage-engine, and version-numbering level. For that reason, rather than assuming the two behave identically, it is wise to consult the documentation of the specific version in use.

How MySQL Works: Client-Server Architecture

MySQL runs as a server process (usually mysqld). Applications connect over a network socket or a local socket, authenticate, and send SQL statements. The server parses those statements, builds a query plan, reads or writes data through a storage engine, and returns the result to the client.

This separation matters: your application code does not need to know how data is stored on disk. It only speaks SQL; the server handles the rest. Many applications written in different languages can connect to the same server concurrently, because MySQL manages connections and concurrency itself. This model cleanly separates the data layer from the application layer and makes scaling easier.

• Connection layer: authentication, session handling, and security.
• SQL layer: parsing, the optimizer, caching, and execution.
• Storage engine layer: a pluggable layer that decides how data is kept on disk.
• File system: table data, indexes, and log files.

Storage Engines: InnoDB and MyISAM

A storage engine determines how a table's data is physically stored, along with its locking and transaction behavior. MySQL has long supported several engines; today the default and most commonly recommended one is InnoDB.

Basic SQL Examples

Working with MySQL means writing SQL to define tables and query data. The example below creates a simple news table and shows a few basic operations.

-- Create a database and table
CREATE DATABASE news_site
  CHARACTER SET utf8mb4
  COLLATE utf8mb4_unicode_ci;

USE news_site;

CREATE TABLE articles (
  id           BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
  title        VARCHAR(200) NOT NULL,
  body         MEDIUMTEXT,
  published_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
  views        INT UNSIGNED NOT NULL DEFAULT 0
) ENGINE=InnoDB;

-- Insert and query data
INSERT INTO articles (title, body)
VALUES ('Sample Title', 'Article body goes here.');

-- Get the 10 most recent articles by date
SELECT id, title, published_at
FROM articles
ORDER BY published_at DESC
LIMIT 10;

-- Add an index on a column to speed up lookups
CREATE INDEX idx_published ON articles (published_at);

Data Types and Schema Design

In a relational database, every column has a data type, and that type affects both storage and query behavior. MySQL offers a broad range of numeric, textual, date-time, and binary types. Choosing the right type reduces disk usage and speeds up comparison and sorting operations.

In schema design, normalization improves consistency by splitting repeated data into separate tables. MySQL can also store semi-structured data with the JSON type, which adds flexibility for fields that do not fit a rigid schema.

Indexes and Performance

Indexes are data structures that let the database find specific rows without scanning the whole table. InnoDB stores the primary key as a clustered index, and secondary indexes point back to that primary key. Sound index design is one of the biggest levers on query performance.

The most common reason a query runs slowly is the absence of a suitable index on the column being filtered or sorted. But adding an index is not free: every write must also update the relevant indexes. Index strategy is therefore built around the balance between reads and writes.

• Indexing frequently filtered and sorted columns speeds up read queries.
• Excessive indexing slows down writes and increases disk usage.
• The EXPLAIN statement shows which indexes a query uses.

-- Inspect a query's execution plan
EXPLAIN SELECT id, title
FROM articles
WHERE published_at >= '2026-01-01'
ORDER BY published_at DESC;

Replication and High Availability

MySQL provides replication capabilities that copy changes from one server to one or more replicas. In the classic approach, a primary server accepts writes while replica servers follow those changes through the binary log.

• Read scaling: spreading read traffic across multiple copies.
• Redundancy: a replica can take over if the primary fails.
• Geographic distribution: keeping copies of the data in different regions.

Replication is not a backup method on its own; data accidentally deleted on one copy can propagate to the others through replication. It therefore complements regular backups rather than replacing them. In a well-designed setup, replication provides high availability while separate backups safeguard disaster-recovery scenarios.

User Management and Security

MySQL has a fine-grained authorization system. You create users and grant each one specific privileges on specific databases and tables. Following the principle of least privilege, giving an application only the permissions it needs is a security fundamental.

-- Create a restricted, application-specific user
CREATE USER 'app'@'10.0.0.%' IDENTIFIED BY 'a-strong-password';

-- Grant read/write only on the relevant database
GRANT SELECT, INSERT, UPDATE, DELETE
  ON news_site.*
  TO 'app'@'10.0.0.%';

FLUSH PRIVILEGES;

• Encrypt connections with TLS/SSL to protect data on the wire.
• Do not use privileged accounts such as root for application connections.
• Keep passwords strong and, where possible, restrict network access to trusted sources.
• Apply updates regularly to close known security vulnerabilities.

Backup and Restore

No database strategy is complete without reliable backups. MySQL offers two fundamental backup approaches: logical and physical. Logical backups export data as SQL statements, while physical backups copy the data files themselves.

# Take a logical backup (mysqldump)
mysqldump -u root -p news_site > backup.sql

# Restore the backup
mysql -u root -p news_site < backup.sql

Licensing: Open Source and Commercial

MySQL is offered under a dual-licensing model. The community edition ships under a free/open-source license, while Oracle also provides commercial editions with extra features and support. Which license fits depends on how you distribute your own product.

MySQL, MariaDB, and Other Alternatives

MySQL is not alone; the relational database world offers many options. Its closest relative is MariaDB, which grew out of MySQL and remains largely compatible. Those looking for richer standard-SQL support and advanced features often evaluate PostgreSQL. At enterprise scale, commercial systems such as Oracle Database may be preferred.

The right choice depends on your workload, your team's experience, your licensing preferences, and your scaling needs. To compare the strengths of different engines, see our main guide.

When Should You Choose MySQL?

MySQL is a strong default especially for web-based, read-heavy projects that expect a mature ecosystem. For content management systems, e-commerce, and news sites, it has been a proven option for many years. Most popular content platforms ship with MySQL support, which means ready availability on hosting providers and a broad plugin ecosystem.

When starting a new project, choosing a system your team is familiar with, whose expertise is easy to find, and that is simple to deploy is often the most pragmatic decision. Because MySQL meets all of these criteria, it is a solid starting point unless a specific reason calls for something else.

• Easy setup with broad hosting and cloud support.
• A large community, plentiful documentation, and a rich tooling ecosystem.
• Transactional safety and row-level locking with InnoDB.
• Flexible growth from small to medium-large scale.

Summary

MySQL is an open-source, mature, and widely adopted relational database. With its client-server architecture, pluggable storage engines, strong indexing, and replication capabilities, it forms the backbone of many web projects. Through the InnoDB engine it offers transactional safety, and weighed alongside alternatives such as MariaDB, PostgreSQL, and Oracle, it provides a solid foundation for most scenarios.