Geographic Distribution and Geo-Scale

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.

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

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.

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.

For this next ‘multi-master MySQL’ blog in our Continuent MySQL Case Study series, we’re focussing on Financial Services Saas providers.

This next blog in our Continuent MySQL Case Study series is a sub-series on the topic of ‘multi-master MySQL’, in which we cover three multi-master MySQL use cases focusing on e-commerce to start with, financial services and telecommunications.

This case study blog discusses how one of our customers, a global SaaS provider for e-signature services, who used to run MySQL master/slave clusters, initially using native MySQL replication started using Tungsten Clustering; enabling them to deploy hybrid-cloud MySQL clusters for continuous operations and migration purposes, while preventing lock-in to any specific cloud vendor.