Transactions with InnoDB
Group related changes into a transaction, with isolation and recovery built into the storage engine.
Read the official guideAll database engines
Managed MySQL
Managed MySQLThe familiar foundation for your web application.
For applications built around MySQL, changing hosting should not mean changing the database. Keep your existing SQL, connectors and migration tools, with server operations in one workspace.
MySQL / a familiar starting pointSTART TRANSACTION;
UPDATE stock SET quantity = quantity - 1
WHERE sku = 'daily-notebook' AND quantity > 0;
INSERT INTO orders (sku, quantity)
VALUES ('daily-notebook', 1);
COMMIT;Working with MySQL
Choose it for the work
it does well.
Understand a slow query
Use EXPLAIN to inspect query plans before adding indexes or choosing a larger server.
Read the official guideConnect with your usual tools
Use established connectors for your language and standard MySQL desktop or command-line clients.
Read the official guideWhere it fits.
Commerce, content platforms, web applications and existing projects already running MySQL.
Before you choose
Check SQL modes, character sets and version compatibility before a move. HA keeps quorum in the primary region; it is not protection against every regional outage.
Your database.
The server work, covered.
The workspace brings connections, access and recovery together. Your application keeps its standard database client.
Connect with confidence
Find your endpoint, port, credentials and certificate together, with examples for standard clients.
Control who gets in
Set allowed IPs and give applications separate users. Review permissions before opening access.
Keep recovery separate
Full backups and recovery logs are stored off-server. Your workspace shows completed coverage.
Give MySQL its own workspace.
Choose a published node type, region and storage. Review your monthly total before checkout.