Clustering Topologies

High Availability (HA) Configurations and Topologies

Continuent Tungsten HA
1 master + 2 failover and read slaves

The Continuent Tungsten HA configuration is designed for any site that strives to ensure constant HA. This configuration ensures the ability to perform maintenance on any DBMS server and still maintain a HA environment capable of supporting a failover at any time. This is the preferred configuration for large transaction processing applications.

Continuent Tungsten HA Plus

Continuent Tungsten HA with Read Scale
1 master + n failover slaves + n read slaves

The Continuent Tungsten HA with Read Scale configuration is ideal for sites that require HA and also need to scale read performance. Media and consumer web sites should consider this option. Continuent Tungsten enables additional read slaves at no performance impact to a HA cluster. Additional read slaves in this configuration are included at no additional subscription charge.
Continuent Tungsten HA Plus with Read Scale

HA and DR Configurations and Topologies

Continuent Tungsten HA with Hot Standby DR Plus
1 master + 2 failover slaves and 1 passive master + 1 passive slave

This configuration extends the HA offered by the Tungsten Basic HA with DR configuration by adding an extra slave for read scaling, and more protection through an additional DR slave. It is suitable for larger applications that need maximum HA but without a full copy of primary site resources on the DR site.

Continuent Tungsten HA Plus with DR

Continuent Tungsten HA and Hot Standby DR Site
1 master + 2 failover slaves plus 1 passive relay master + 2 passive slaves

The Continuent Tungsten HA with Read Scale and DR Site offers high local availability and performance scaling with the additional protection of a full replacement DR site. This option is suitable for customers with active sites that need the highest levels of HA protection.

Tungsten HA Plus and DR site

Multi-site Configurations and Topologies

Continuent Tungsten HA and Active DR Site (aka Composite Cluster)
1 master + 2 failover slave and 1 active relay master + 2 active slaves

The Continuent Tungsten Composite Cluster configurations provide highly available local operation plus an active failover site that is also available for reads. They are well suited for customers who seek the highest level of HA protection without altering applications, with the ability to operate applications on both sites.

Continuent Tungsten HA Plus with active failover

Continuent Tungsten Multi-Master
1 master + 2 failover slaves and 1 master + 2 failover slaves

The Continuent Tungsten Multi-Master links highly available clusters across sites to enable constant availability for updates in two or more locations separated by high-latency networks. It is recommended for applications like credit card payment gateways or online testing services that must always be available for business.

Continuent Tungsten Multi-Master

 

 

Examples of Replication Topologies

 

Real-time replication from Oracle to Oracle
Oracle master + Oracle slave or Oracle RAC + Oracle RAC or Oracle Slave

The Continuent Tungsten real-time Oracle-to-Oracle replication is ideal for customers seeking an efficient, low-cost solution HA solution for Oracle databases. Tungsten works with individual Oracle instances as well as Oracle RAC.

Think "Oracle GoldenGate without the price tag!"

Typically requires three to five (3-5) days of production deployment consulting and training.

Real-time replication from Oracle to Oracle

Real-time replication between MySQL and Oracle
MySQL master + Oracle slave, Oracle master + MySQL slave

The MySQL-Oracle configurations are ideally suited for integrating systems that contain both MySQL as well as Oracle applications. Examples include MySQL sales apps that transfer transactions to Oracle for order fulfillment or reporting, and MySQL applications that publish legacy Oracle application data on the web.

Typically requires three to five (3-5) days of production deployment consulting and training.

Real-time replication between MySQL and Oracle

Real-time replication from Tungsten Cluster to Oracle
MySQL master with 2 failover slaves plus an Oracle slave

The Continuent Tungsten cluster-to-Oracle replication ensures proper availability of the MySQL source data. For example, it is recommended for servers that aggregate data on the way to Oracle to avoid loss of a critical link in business processing should the aggregation server fail or need to go offline for maintenance.

Typically requires three to five (3-5) days of production deployment consulting and training.

Real-time replication from Tungsten cluster to Oracle

Replication to real-time analytics and Big Data
MySQL/Oracle to Hadoop, MySQL/Oracle to MongoDB, MySQL/Oracle to Vertica (others upon request)

MySQL/Oracle to analytics and NoSQL replication enables users to publish transactions from MySQL and Oracle systems in real-time to Hadoop, MongoDB and Vertica. This deployment model is recommended for businesses that need to deliver complex analytics quickly on rapidly changing data.

Typically requires five to ten (5-10) days of production deployment consulting and training.

Replication to Real-Time Analytics and Big Data