Transactional Standalone Availability

Overview

The following availability details pertain to SkySQL's MariaDB Platform for Transactions in a Transactional Standalone topology.

Amazon Infrastructure

MariaDB SkySQL services on AWS rely on Elastic Kubernetes Service (EKS), which is a component of Amazon Web Services (AWS). MariaDB SkySQL inherits many availability features from EKS and AWS:

  • The resiliency features of EKS.

  • The auto-healing functionality of Kubernetes.

  • Amazon's goal to have 99.95% up-time, as mentioned in the SLA for EKS.

Google Infrastructure

MariaDB SkySQL services on GCP rely on Google Kubernetes Engine (GKE), which is a component of Google Cloud Platform (GCP). MariaDB SkySQL inherits many availability features from GKE and GCP:

  • The resiliency of regional GKE Kubernetes clusters which include multiple zones within a region.

  • The auto-healing functionality of Kubernetes.

  • Google's goal to have 99.5% up-time, as mentioned in the SLA for GKE.

Powered by Kubernetes

MariaDB SkySQL services run in containers powered by Kubernetes. MariaDB SkySQL inherits many availability features from Kubernetes' self-healing functionality:

  • Failed containers are automatically restarted.

  • Unhealthy containers are automatically killed.

  • Dead containers are automatically replaced.

  • All of this happens in a way that is transparent to the user.

Production Readiness

MariaDB Platform for Transactions in a Transactional Standalone topology is resilient enough to handle non-critical applications that allow for short periods of downtime in the case of failure.