Blog

Following on from our recent newsletter and the message from Eero Teerikorpi, Founder and CEO, in this blog I will set out the outline and plan for the work we are currently undertaking to make a number of changes within the terminology used in our product and communications.

Watch our latest on-demand webinar: Deploying Hybrid & Multi-Cloud Applications With Ultimate MySQL Availability. Learn about the pros and cons of single cloud region vs multi-region cloud deployments … and more.

We’ve been receiving requests recently from MySQL users wanting to understand how InnoDB Cluster compares to Tungsten Clustering, our MySQL HA, disaster recovery, and geo-clustering solution. In response we have come up with this comparative outline, looking at some of the key features of each.

This blog discusses some best practices for using multiple filesystems on MySQL database servers and how to achieve the best performance with them, while avoiding some of the possible pitfalls.

Do-it-Yourself (DIY), database migration; what other approaches are there to challenges of MySQL availability, reliability, scalability and application performance?

Continuent Tungsten enables greater application availability and performance especially across WAN, it saves tons of manual labor and headache, it’s backed by premium 24/7/365 support, and it enables all sorts of new freedom and possibilities for data infrastructure including multi-cloud, hybrid-cloud, and advanced, real-time analytics.

This blog explores the best practices for deploying Tungsten Clustering for MySQL across Availability Zones, outlining the approaches for best high availability, fast response times, and load balancing recommendations.

People approach Continuent for many reasons, including: MySQL Continuous Operations: their business is using MySQL for business-critical applications that require zero downtime, including for maintenance updates MySQL Performance: their application performance and user experience are suffering due to a faltering MySQL backend MySQL Scaling and geo-scaling: they're scaling up and taking prudent preventative measures to lay a strong foundation based on anticipated growth, within region, cross the regions and

Continuent is pleased to announce the 6.1.4 versions of its Tungsten Clustering and Tungsten Replicator software products for MySQL, MariaDB and Percona Server.

The new releases introduce support for the MySQL 8.0.20 binlog compression feature, improvements and fixes to command line tools, and more.

We’re also announcing the release of Tungsten Dashboard 1.0.8.

We’ve created a new space on our website for our flagship product Tungsten Clustering. This blog invites you to take a tour of the new product section and to get in touch with us for your MySQL MySQL High Availability, Disaster Recovery and/or Geo-Clustering needs.

Introducing our new website and its many new features and content elements: the home of Continuent - the MySQL Availability Company.

On Monday April 27th, MySQL released a much anticipated patch release 8.0.20. Along with many bug fixes and improvements, a new property was introduced - binlog-transaction-compression. During our own testing we have discovered an incompatibility with this property. Read on for more information.

An overview of a Tungsten topology that doesn’t get much attention: the Cluster-Slave, which is an easy way to get data resiliency and integration, with features that make it ideal for big data analytics, reporting, and backups.