Blog

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.

In the current MySQL ecosystem, organizations must focus on high availability and fault tolerance to ensure business continuity and maintain customer trust. A recent inquiry to prominent tech executives identified five key themes for achieving this: multi-region deployment to prevent single points of failure, automated self-healing for quick issue resolution, redundancy through system duplication, microservices architecture for improved resilience, and load balancing for efficient resource management. Continuent's Tungsten Clustering solution aligns with these strategies, making it an optimal choice for organizations managing critical workloads.

Cloud-based managed MySQL data services have become popular choices for businesses. While these services offer advantages, they also come with a host of drawbacks that can impact performance, control, and costs. This post explores these key drawbacks in detail and compares those to Tungsten Clustering running in the cloud, also multi-cloud, hybrid-cloud and on-premises.

It may seem arduous, but there are ways to build a database stack where you have full control of your data and data operations. For mission-critical applications that must perform continuously 24/7/365, it might make a lot of sense to consider, as there are many benefits to taking control of your mission-critical data and operations. Below are a couple important points to consider when doing an analysis of what’s best for your application and end users.

Migrating to the cloud with zero downtime is a problem that companies running mission-critical applications have to solve, but not on their own. If you’re running a MySQL or MariaDB database it can be easy. Many of our customers have done this successfully, simplifying their overall Cloud migration process by making the database layer easy to move. It’s one less thing to worry about.

You’ve seen the recent news about AWS outages; enterprises have to think about where their physical AWS data centers are and treat them as a single point of failure. As such, enterprises running business-critical and mission-critical applications are accounting for geography of public cloud resources in their business-continuity plans. Learn about a solution for continuous operations for your MySQL database that’s a step above traditional MySQL Disaster Recovery (DR).

In this blog post we will explore the procedure for getting an email notification every time a file is uploaded to an AWS S3 bucket. Instead of having to poll the AWS S3 bucket manually for new uploads, we wanted a way to be notified by email every time a file landed. The solution was a combination of an SNS Topic used by an SNS Subscription, and called by an S3 bucket Event notification.

A VPC peering connection is a networking connection between two VPCs that enables you to route traffic between them using private IP addresses. Instances in either VPC can communicate with each other as if they are within the same network. This blog provides step-by-step instructions on how to set up VPC networking between regions (also known as inter-region VPC peering connections).

As we are all being pushed to the limit to meet unprecedented demands online, the pandemic shined a light on many new frontiers and achievements in technology. This blog is about continuous MySQL database operations when you have a global user base, particularly the VMworld 2021 Global Multi-Cloud conference.

MySQL High Availability (HA) is typically what architects and technologists look for in building business-critical and mission-critical applications, and they aspire to measure MySQL uptime in 4 or preferably more “nines.” This blog explores the modern world of continuous MySQL operations - cross-region, global, hybrid-cloud, and multi-cloud - and why you might need a different approach.

This is the next in our ‘High Noon’ comparison series in which we look at the main solutions for MySQL high availability, disaster recovery and geographic distribution. Here we focus on highly available, geo-scale, multi-region MySQL for mission-critical sites and apps with Microsoft Azure Database for MySQL as compared to native MySQL, MariaDB clusters with Continuent Tungsten in the cloud, hybrid-cloud, multi-cloud or on-premises.

This is the next blog in our ‘High Noon’ comparison series in which we look at the main solutions for MySQL high availability, disaster recovery and geographic distribution. Here we focus on highly available, geo-scale, multi-region MySQL for mission-critical sites and apps with Google Cloud (GCP) for MySQL as compared to MySQL, MariaDB clusters with Continuent Tungsten, the only complete, fully-integrated clustering solution for MySQL - on-premises, in the cloud, hybrid-cloud or multi-cloud.