Blog

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

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.

How to build a multi-region, multi-master MySQL cloud database back- end capable of serving a global, high-volume cloud contact center: this global SaaS provider is a Cloud Contact Center solution provider, who needs to deliver up-to-date data to clients as quickly as possible.

This case study of a global SaaS provider looks at how our customer migrated from Amazon RDS to a truly global, geo-distributed multi-master Tungsten Clustering solution.

This MySQL high availability and disaster recovery use case is based on a customer of ours who is a government-regulated lottery service and who needs 24x7x365 operations as well as be able to perform maintenance without any disruption to their public facing gaming website.

Version 6+ of Tungsten Clustering comes with a host of improvements for your Multi-Site Multi-Master topology (MSMM); this is partly why it has a new name: Composite Master-Master (CMM). Probably the most notable improvement is that the Managers are more aware. What does that mean?

This case study blog discusses a Telco provider that specializes in roaming, i.e. complete connectivity solutions around the world. It is our third ‘multi-primary MySQL’ blog in our Continuent MySQL Case Study series.