MySQL

Open-source single-primary relational database with asynchronous replication.

Provider
default
Category
Data
Properties · 2 set by this component
propertytypevaluesrequiredkind defaultthis component
appendOnly · advancedboolean—nofalseinherited
backupEnabledboolean—nofalseinherited
backupRetentionDaysinteger—no—inherited
commitProtocol · advancedenumsingle | two-phasenosingleinherited
concurrencyControl · advancedenumpessimistic | optimistic | constraintno—▸ pessimistic
distributedboolean—nofalseinherited
encryptionAtRestboolean—nofalseinherited
idEncodesShard · advancedboolean—nofalseinherited
instancesinteger—no—inherited
managedboolean—nofalseinherited
multiWriterboolean—nofalseinherited
replicaFanout · advancedinteger—no—inherited
replicaOfref—no—inherited
replicationenumnone | async | syncnonone▸ none
shardKeystring—no—inherited
shardedboolean—nofalseinherited
storageEngine · component propertyenuminnodb | myisamnoinnodbinherited
version · component propertystring—no—inherited
Rules that apply · 6

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

business-updates-without-index-propagation

Application servers write this database and the design keeps a search index, but nothing captures the database's changes. The index then depends on the application writing to both places, and the two drift apart silently.

  • — all of these hold:
  • — the node has at least one synchronous incoming edge from an app-server
  • — the design contains a node of kind search-index
  • — this does not hold:
  • — the node has at least one outgoing edge to a change-data-capture
datastore-missing-backup

A system of record with backups off, or with no retention period stated, cannot be restored. The loss is discovered on the day it matters.

  • — any of these hold:
  • — the node's `backupEnabled` is false
  • — the node's `backupRetentionDays` has no value
datastore-single-region

The design promises multi-region availability, but this datastore sits in one region and does not replicate. A region outage takes the system of record with it.

  • — all of these hold:
  • — the design requirement `availability.multiRegion` is true
  • — the node sits inside exactly 1 region group
  • — the node's `replication` is "none"
read-heavy-path-without-cache

The design states a read-heavy workload and application servers read this datastore directly, yet the design has no cache anywhere. Every read pays a database round trip.

  • — all of these hold:
  • — the design requirement `traffic.readWriteRatio` is a number greater than 10
  • — the node has at least one synchronous incoming edge from an app-server
  • — this does not hold:
  • — the design contains a node of kind cache
read-replica-as-sole-scaling

Asynchronous read replicas scale reads only. When the store is neither sharded nor distributed the writes still land on one primary, so the replicas add nothing at the declared peak.

  • — all of these hold:
  • — the node's `replication` is "async"
  • — the node's `sharded` is false
  • — the node's `distributed` is false
  • — the node's declared requests per second is more than 5000
single-writer-primary-at-peak-qps

A single-writer, unsharded relational primary has a throughput ceiling. Declaring more than five thousand requests per second against it means the peak finds that ceiling in production.

  • — all of these hold:
  • — the node's `multiWriter` is false
  • — the node's `sharded` is false
  • — the node's declared requests per second is more than 5000
Use it in a design
nodes:
  - { id: "mysql", component: "mysql" }
Other SQL database products · 75
ApsaraDB for OceanBasealibaba-oceanbasealibabacloudsql-databasePolarDBalibaba-polardbalibabacloudsql-databasePolarDB-Xalibaba-polardb-xalibabacloudsql-databaseApsaraDB RDSalibaba-rdsalibabacloudsql-databaseAmazon Auroraauroraawssql-databaseAmazon Aurora DSQLaws-aurora-dsqlawssql-databaseOracle Database@AWSaws-oracle-databaseawssql-databaseAmazon RDSaws-rdsawssql-databaseAmazon RDS Customaws-rds-customawssql-databaseAzure Database for MySQLazure-database-for-mysqlazuresql-databaseAzure Database for PostgreSQLazure-database-for-postgresqlazuresql-databaseAzure HorizonDBazure-horizondbazuresql-databaseOracle AI Database@Azureazure-oracle-databaseazuresql-databaseAzure SQL Databaseazure-sqlazuresql-databaseAzure SQL Managed Instanceazure-sql-managed-instanceazuresql-databaseSQL Server on Azure Virtual Machinesazure-sql-server-vmazuresql-databaseCloudflare D1cloudflare-d1cloudflaresql-databaseCituscitussql-databaseCockroachDBcockroachdbsql-databaseCockroachDB Cloudcockroachdb-cloudsql-databaseDatomicdatomicsql-databaseIBM Db2db2sql-databaseEDB Postgres Advanced Serveredb-postgressql-databaseClaris FileMaker Serverfilemakersql-databaseFirebirdfirebirdsql-databaseIBM Informixinformixsql-databaseActian Ingresingressql-databaseInterBaseinterbasesql-databaseInterSystems IRISintersystems-irissql-databaseMariaDB Servermariadbsql-databaseNeonneonsql-databaseOceanBase Databaseoceanbasesql-databaseProgress OpenEdgeopenedgesql-databaseOracle Databaseoracle-dbsql-databasePlanetScaleplanetscalesql-databasePostGISpostgissql-databasePostgreSQLpostgressql-databaseRelational databaserelational-databasesql-databaseSAP Adaptive Server Enterprisesap-asesql-databaseSAP HANAsap-hanasql-database
and 35 more → SQL database page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# MySQL: single-primary relational database; replication is asynchronous and opt-in.
schemaVersion: "1"
type: "component"
id: "mysql"
kind: "sql-database"
provider: "default"
docs: "https://dev.mysql.com/doc/refman/8.4/en/"
defaults:
  replication: "none"
  concurrencyControl: "pessimistic"
properties:
  version:
    type: "string"
  storageEngine:
    type: "enum"
    values: ["innodb", "myisam"]
    default: "innodb"

The same page as markdown, for an agent: /catalogue/components/mysql.md