Azure Database for MySQL runs the open-source MySQL database system as a fully managed Azure service. It offers automatic backups, scalability, and security features while retaining the MySQL wire protocol. If an application and its tools already use MySQL, that compatibility makes moving to a managed service appealing. section 10.3.2
Check the trade-offs before choosing it:
- Performance: MySQL can handle high traffic and supports JSON data, but optimal performance may require manual tuning; complex queries can be slower than on some alternatives. section 10.3.2
- Cost: It is generally less expensive than Azure SQL Database, but the compute tier matters. Storage, backup storage, and network traffic can add to the bill. section 10.3.2
- Recovery and security: Automatic backups and security features help, but out-of-the-box disaster recovery is limited, and some security features are less robust than those of Azure SQL Database. section 10.3.2
Choosing a database for an online bookstore
A bookstore with existing MySQL applications might favor compatibility and a lower starting cost. If its priorities instead put greater weight on disaster recovery, security, and peak-period performance, Azure SQL Database may be the better choice. section 10.3.4 section 10.3.2
C:/> az mysql flexible-server create --name BanningBooksMySQLServer --resource-group BanningRG --location australiaeast --admin-user adminuser --admin-password <your_password> --sku-name Standard_B1s --storage-size 100 --version 8.0.21
The Azure CLI example creates a MySQL flexible server with a resource group, location, administrator credentials, compute SKU, storage size, and MySQL version. Flexible server also supports starting and stopping the server. section 10.3.2
