Proxy

SmartScale is a special mode of the Tungsten Connector (aka Tungsten Proxy), which allows read requests to be intelligently routed to either a replica or the primary to ensure that the data returned is not stale. This feature is available when the Connector is running in the application-layer Proxy mode. Learn more about the behavior of SmartScale in this blog.

How the Continuent Proxy selects database cluster nodes for executing read operations.

View this presentation to learn about two types of (MySQL) database proxies, which we refer to as ‘fast & simple proxy’ and ‘intelligent proxy’; and how transparent failover and read-write splitting works for these.

Watch our new on-demand webinar: “An introduction to database proxies (for MySQL)”. From a simple database connectivity scenario all the way through to advanced database connectivity setups and proxy functionalities, this webinar provides a solid introduction to database proxies (for MySQL).

Why does the DIY approach fail to deliver vs. the Tungsten Clustering solution for geo-distributed MySQL multimaster deployments? Before we dive into the 10 reasons, note why commercially-supported enterprise software is less risky and in fact less costly.

The power of Tungsten Clustering for MySQL / MariaDB is its built-in intelligent MySQL proxy, known as the Tungsten Connector. The Connector has built-in read-write splitting capabilities, and it is also possible to configure different algorithms which select the appropriate slave (i.e. Round-Robin or Lowest-Latency).

Database Proxies provide a single entry point into MySQL for the calling client applications. Proxies are wonderful tools to handle various situations like a master role switch to another node for maintenance, or for transparency with read and write connections. However, when the time comes to perform the switch action, all of the calling clients have been funneled through the proxy, so identification of the calling host from the database itself becomes difficult.

Part of the power of Tungsten Clustering for MySQL / MariaDB is its intelligent MySQL Proxy, known as the Tungsten Connector. Tungsten Connector has three main modes, and depending on the type of operations you are performing (such as if you need read-write splitting), we help you choose which mode is best. Hence the question, "How can I tell which Tungsten Connector mode I am using: Bridge, Proxy/Direct or Proxy/SmartScale?"

In this blog post we will discuss how to use the Tungsten Connector keep-alive feature to ensure long-running MySQL & MariaDB/Percona Server client sessions stay connected in a Tungsten Cluster.

When it comes to zero downtime, proxies are the first line components of a cluster. In order to achieve High Availability (HA) for MySQL, MariaDB and Percona Server, a commonly deployed setup consists of configuring load balancers (hardware or software) on top of those proxies.

In this blog post, we describe the new Read Affinity tuning feature of the Tungsten Connector.

Tungsten Connector read affinity now supports multiple dataservices with ordering and exclusion (only one was previously allowed).

You may now fine-tune the affinity per user in user.map and via the global tpm configuration option connector-affinity.

In this blog post, we demonstrate how to convert a single standalone MySQL cluster into a Composite Primary/DR topology running in two data centers.