The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.
In this blog post we will discuss the basics of how to implement and use filters in the Tungsten Replicator.
Managing a single cluster takes time and attention, and handling multiple clusters spread out over many sites is even more demanding. Tungsten Clustering offers a graphical administration tool called the Tungsten Dashboard™ to help with your management burden. You are able to view, monitor and maintain all of your clusters all in one place.
Think about it - your global, cloud-based application needs to be online and available for the business to run. Downtime is to be avoided like the plague. Perhaps you even have multiple cloud providers to span.
How do we create a database service layer that handles all kinds of failures?
Achieving software upgrades without downtime is a challenge that few software products can handle, or even try to. Tungsten Clustering is one that can!
The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source databases to various targets like Vertica, Kafka, Redshift and so on.
The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target. The Tungsten Replicator is embedded into the Tungsten Clustering solution to provide core replication services, replacing native MySQL replication.
In this blog post we will discuss a few of the commands that will make your life easier.
Think about it - your application needs to be online and available for the business to run. Downtime is to be avoided like the plague. The buzz is all about five nines of uptime.
How do we as systems architects, DBAs and sysadmins create an environment where routine maintenance is not a thing to be feared and put off, but embraced to allow for proper and needed updates and upgrades to take place?
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.
Users seeking high availability, disaster recovery and zero downtime maintenance operation for business-critical MySQL applications face confusing choices. Is multi-master or master/slave clustering better? What about synchronous versus asynchronous...
