Blog

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.

What are some strategies for improving performance when applying to a MySQL target database with Tungsten Replicator?

Tungsten Dashboard v1.0.16 is now available, featuring a crucial bug fix that resolves a regression in the configuration processing function. This update ensures smoother and more reliable performance, helping you maintain seamless workflows. Update today to benefit from the enhanced stability of your dashboard experience.

Prometheus and Grafana are open source tools that can be used for monitoring MySQL clusters. Prometheus can be used to collect metrics from MySQL clusters, and Grafana can be used to visualize the metrics. Starting with Tungsten v7, using the new Tungsten Prometheus Exporter feature, it’s become easy to leverage the best these powerful monitoring tools have to offer.

This post covers some standard Nagios checks that would help keep your Tungsten cluster nodes running MySQL / MariaDB / Percona Server healthy.

Your MySQL database cluster contains your most business-critical data; in this post, we discuss how to ensure proper performance under load.

In this blog post we explore various options for performance tuning MySQL server for better replica replication performance.

In this blog post we will define what a split-brain scenario means in a MySQL database cluster, and then explore how a Tungsten MySQL database cluster reacts to a split-brain situation.