Transactions

MariaDB SkySQL includes several services for transactional workloads, supporting small dev/test environments up to mission-critical production environments requiring 24x7x365 operation.

Topology Options

  • MariaDB Platform for Transactions in HA (Primary/Replica) topology is designed to meet the demands of 24 hours a day, 7 days a week, 365 days a year operation for production transactional workloads. See HA (Primary/Replica) Transactional for details. Available on AWS and GCP.

  • MariaDB Platform for Transactions in Galera topology is designed to meet the demands of 24 hours a day, 7 days a week, 365 days a year operation for transactional workloads. See Galera Transactional for details. Available on GCP.

  • MariaDB Platform for Transactions in Transactional Standalone topology is designed to serve as a development and test environment for transactional workloads. See Transactional Standalone for details. Available on AWS and GCP.

  • Also available: MariaDB Platform for Distributed SQL in Distributed Transactions topology enables distributed SQL workloads with fault tolerance. See MariaDB Platform for Distributed SQL for details. Available on AWS and GCP.

Comparison of MariaDB Platform for Transactions Topologies

HA (Primary/Replica)

Galera

Transactional Standalone

Workload Optimization

Transactional

Transactional

Transactional

Server

MariaDB Enterprise Server 10.5 or 10.4

MariaDB Enterprise Server 10.5 or 10.4

MariaDB Enterprise Server 10.5 or 10.4

Storage Engine

InnoDB

InnoDB

InnoDB

Storage

EBS Provisioned IOPS (AWS)
Zonal SSD Persistent Disk (GCP)

Zonal SSD Persistent Disk

EBS Provisioned IOPS (AWS)
Zonal SSD Persistent Disk (GCP)

Number of ES Instances

1 Primary
1-5 Replicas

3, 5, 7, or 9 cluster nodes

1

Replication

Async/Semi-sync MariaDB Replication

Galera Cluster (virtually synchronous)

Yes

Load Balancing

MariaDB MaxScale-powered Load Balancing

MariaDB MaxScale-powered Load Balancing

No

Failover

MariaDB MaxScale-powered Failover

MariaDB MaxScale-powered Failover

No

Production-Ready

Yes

Yes

No

Development/UAT-Ready

Yes

Yes

Yes

For distributed SQL with fault tolerance, see MariaDB Platform for Distributed SQL for details.

Workload Examples

Transactional workloads are generally characterized by a fixed set of queries.

Some examples of transactional workloads:

  • Sales records for an e-commerce website.

  • Banking transactions for a back-end banking system.

  • Tracking appointments or patient data for a healthcare system.

Screenshots

Launch interface highlighting Transactional Service
Launch interface highlighting HA (Primary/Replica) selector

FAQ

These questions and answers pertain to the MariaDB Platform for Transactions service.

For a complete list of questions and answers, see the SkySQL Frequently Asked Questions (FAQ) list.

What features does MariaDB Enterprise Server provide?

Features of MariaDB Enterprise Server include:

  • Enterprise-optimized builds with backports of critical fixes, improved code stability, and enterprise enhancements.

  • Compatibility with most programming languages and clients that work with MariaDB or MySQL, for off-the-shelf integration to your stack.

  • Online schema changes with InnoDB's Instant ALTER.

  • MariaDB Enterprise Audit for enhanced audit logging.

  • MariaDB Enterprise Backup for hot online backups.

InnoDB is the supported storage engine for customer-created tables in MariaDB Platform for Transactions services, which are dependent on the enhanced capabilities and compatibility of InnoDB for transactions, backups, crash recovery, replication, and other features.

What is the SLA?

See Service Availability (SLA) for complete details.

Short answer, HA (Primary/Replica) topologies deliver 99.95% for most customers, and an elevated 99.995% for Power Tier customers.

SLA is not provided for Transactional Standalone services, as High Availability (HA) features are not enabled in single-node configurations.

What is configurable?

At time of service launch, region, instance sizes and storage sizes, MariaDB Enterprise Server version, and replica count (where applicable) are configurable.

After launch, MariaDB Enterprise Server and MariaDB MaxScale (where applicable) are configurable using SkySQL's Configuration Manager. A full list of configurable parameters is available.

Is inbound replication supported?

Inbound replication (to MariaDB SkySQL) is available for the HA (Primary/Replica) topology. Additionally, cross-region replicas for disaster recovery are available to Power Tier customers.

How are backups performed?

Automated nightly backups are performed with MariaDB Enterprise Backup, which enables hot online backups. MariaDB Enterprise Backup breaks up backups into non-blocking stages so writes and schema changes can occur during backups.

How do I monitor my database?

SkySQL Monitoring provides real-time status and metrics. SkySQL Monitoring includes server-level and service-level monitoring, replication monitoring, and monitoring of the MariaDB MaxScale load balancer (where applicable).

What support is available?

While all SkySQL instances include Standard Support, enhanced support plans are available to meet the needs of mission-critical deployments requiring 24x7 support. Enterprise and Platinum support plans are optional.

An option available to customers with Enterprise or Platinum support plans, SkyDBA further extends the premium support experience and the capabilities of your in-house DBAs with the backing from a global team of expert MariaDB DBAs, available 24/7 for the most severe (S1) issues. MariaDB's SkyDBAs manage your MariaDB SkySQL databases both proactively and reactively so you can focus on your core business.

What if I have other requirements?

SkySQL Power Tier is a premium service offering for MariaDB SkySQL customers who have the most critical requirements for uptime, availability, performance, and support.