Blog

High availability keeps MySQL and MariaDB applications running through routine local failures, while disaster recovery restores service after a site or regional outage. This article explains how RTO, RPO, distance, synchronous replication and asynchronous replication shape each strategy, and how Continuent Tungsten Cluster combines local HA with multi-site DR.

Challenges of running MySQL on Kubernetes and how Operators ensure reliability through replication, failover, and observability.

Learn why Kubernetes alone isn’t enough for running stateful databases and how Operators solve challenges like failover, scaling, backups, and upgrades. Discover how Tungsten Operator brings proven MySQL clustering, replication, and enterprise-grade HA/DR into Kubernetes.

After two decades of helping enterprises achieve continuous MySQL operations, we've probably seen it all. The midnight calls about failed failovers. The "highly available" systems that went down for hours during a simple maintenance window. The multi-million-dollar applications that were brought to their knees by a single database node failure.

Discover how Tungsten Cluster v8 builds on the already powerful v7, adding Kubernetes support, REST API v2, stronger security, and lots of enhancements to redefine MySQL clustering.

In this blog we take a look at how you can use Tungsten Replicator to replicate data from multiple sources, and merge into a single target using 3 simple yet effective filters.

This article explores some of the leading MySQL — also including MySQL variants MariaDB and Percona Server — high availability (HA) and disaster recovery (DR) solutions – in alphabetical order, including AWS Aurora, Continuent Tungsten, DIY MySQL clusters, Galera Cluster, and MySQL InnoDB Cluster.

Cloud-based managed MySQL services like Amazon Aurora promised simplicity, scalability, and cost savings. But as adoption grows, many organizations are uncovering hidden costs, operational challenges, and limitations. This blog explores why companies are migrating back to on-premises MySQL and how solutions like Tungsten Clusters are empowering them to regain control, cut costs, and ensure flexibility for their database infrastructure.

In the current MySQL ecosystem, organizations must focus on high availability and fault tolerance to ensure business continuity and maintain customer trust. A recent inquiry to prominent tech executives identified five key themes for achieving this: multi-region deployment to prevent single points of failure, automated self-healing for quick issue resolution, redundancy through system duplication, microservices architecture for improved resilience, and load balancing for efficient resource management. Continuent's Tungsten Clustering solution aligns with these strategies, making it an optimal choice for organizations managing critical workloads.

Standards allow modern systems to advance, and the REST specification is one very important example. Since this post is about the Tungsten API in specific, let me simply say this - a RESTful API adheres to six principles: Client-server, stateless, cacheable, uniform interface, layered system and optionally code on demand. As part of the watchability/monitoring goal, our software as of version 7.0.0 includes a proper RESTful API - what we call APIv2. This API is fully documented and public.

Tungsten Clustering allows for many types of maintenance to happen with no downtime at all. This blog post will explore how to upgrade the actual MySQL Server on all cluster nodes with zero downtime. These same steps may be used to upgrade the MySQL server or patch the OS.

Explore the latest release of Tungsten Clustering & Tungsten Replicator! This new version v7.1.4 brings critical improvements, new features, and bug fixes, ensuring enhanced performance, stability, and functionality for your database management.