- Products & Solutions
- About Us
This blog article discusses why and how we use Ansible (automation tool for pre-configuring MySQL servers) for Tungsten purposes at Continuent, including a step by step description on how to use Ansible (including source code).
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.
This is the first in a series of use case blogs. It discusses the concept of ‘Geo-scale MySQL’ - or how to build a global, multi-region MySQL cloud back-end capable of serving hundreds of user accounts.
The Slow Software Movement is spreading with SaaS companies going global...and their software is the furthest from “slow.” In this blog, a Customer Success Manager at Continuent writes about some observations in her five years of listening to customers and prospects.
This blog explains data replication and clustering in a way that anybody can understand.
Continuent has traditionally had a relaxed policy about Linux platform support for customers using our products.
While it is possible to install and run Continuent Tungsten products (i.e. Cluster/Replicator/etc.) inside Docker containers, there are many reasons why this is not a good idea.
In this blog post, we talk about how to run applications across multiple clouds (i.e. AWS, Google Cloud, Microsoft Azure) using Tungsten Clustering. You want your business-critical applications to withstand node, datacenter, availability-zone or regional failures. For SaaS apps, you also want to bring data close to your application users for faster response times and a better user experience. With cross-cloud capability, Tungsten also helps avoid lock-in to any particular cloud provider.