Blog

Learn how to optimize MySQL replication performance in Tungsten Cluster by tuning the Applier settings. Improve replication speed, minimize commit overhead, and balance data availability with advanced tuning techniques.

Discover the truth behind the cloud repatriation trend and why compute flexibility is the real trend for modern IT strategies. This blog explores the growing shift toward hybrid-cloud solutions, balancing cloud scalability with on-premises control to optimize costs, performance, and compliance. Learn how Tungsten Cluster enables seamless data replication, high availability, and database flexibility across cloud and on-premises environments.

Managing Tungsten Cluster configurations can be challenging, especially when dealing with powerful, yet complex tungsten.ini files. To simplify the process, the new tpm ini command provides an easy way to create, validate, and manage configuration files, helping database administrators streamline their workflow. This new command is available as part of our upcoming V8 software release.

Learn what triggers Tungsten Cluster failsafe-shun and how it helps maintain high availability in MySQL database clusters. Discover key factors and best practices for managing automatic node shunning.

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.

Replication is one of the most critical components of database management, especially in an Active-Active multi-primary composite cluster. However, with great flexibility comes the occasional hiccup. If you’re grappling with intermittent replication failures for a table in your Tungsten Cluster setup, here are five practical approaches to diagnose and resolve the issue.

Discover the benefits of Tungsten Active-Active Clustering for MySQL. Learn how this solution ensures high availability, scalability, low-latency data access, and disaster recovery for businesses with global operations.

Discover the story behind Continuent's logo, showcasing two swans that represent the company's Finnish heritage and dedication to lasting customer partnerships. These swans embody both the elegance of seamless operations and the hard work of the Continuent team in delivering top-tier MySQL high availability and disaster recovery solutions. The logo reflects Continuent's unwavering commitment to reliability, stability, and ensuring zero downtime for its customers.

Securing your cloud environment is now more critical than ever. As organizations increasingly rely on cloud platforms like Amazon Web Services (AWS), the potential for security breaches and unauthorized access becomes a pressing concern. AWS CloudTrail is a powerful tool that can help you monitor and detect suspicious activities in your AWS account. This blog post will guide you through the process of leveraging AWS CloudTrail to detect account intruders and strengthen your overall security posture.

Tungsten Clustering ensures high availability with robust failover capabilities, driven by the Tungsten Manager's health checks and predefined rules. In this blog post, we explore key processes like handling heartbeat gaps, network partitions, and availability checks. We also provide tips for tuning parameters to optimize performance and maintain a resilient database cluster.

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.