TimesTen In-Memory Database
for Extreme Performance

What is the best High Availability option for TimesTen?

Doug Hood
Evangelist for Oracle TimesTen, Oracle In-Memory and Oracle NoSQL

Almost all TimesTen In-Memory Database customers use some form of high availability configuration as they want high performance RDBMS solutions without a single point of failure.

Not all customers have the same sort of applications or availability requirements, so they have to choose which TimesTen replication configuration best suits them.  

The following picture shows a subset of the possible replication configurations: Summary of TimesTen Replication Options

There are two main types of Replication, Active Standby Pair and Classic Replication. Active-Active, N-Way and Propagation are examples of TimesTen Classic Replication.

The following picture summarizes the main differences between Active Standby Pair based and Classic Replication:

Active Standby Pairs and Classic Replication

Active Standby Pair replication schemes can also optionally be configured to include a set of read only subscriber databses:

Active Standby Pair with Read Only Subscribers

For 'classic replication' (ie non active standby pair configurations) there are several options.

Replicating selected DB objects to multiple subscribers

Classic Replication with different DB objects

Split workload bidirectional replication

Classic Replication Split Workload

Distributed Workloads

Classic Replication Distributed Workload

Another thing to consider for replication configurations is whether the data is sent synchronously or asynchronously.

Asynchronous Replication

Asynchronous Replication

Return Two Safe (synchronous replication)

Return Two Safe Replication

Return Receipt (synchronous replication)

Return Receipt Replication

Summary of synchronous and asynchronous replication options

Summary of sync and async option

If you need to support read/write caching for Oracle 11g/12c data with TimesTen Application Tier Database Cache, then you have to use one of the Active Standby Pair configurations. Active Standby Pair replication configurations are the simplest to understand, configure and manage.

The split workload and distributed workload configurations for Classic Replication give more flexibility, but careful consideration is needed to avoid and/or mitigate write/write conflicts.

Replication Configuration Choices

The active standby pair and classic replication configurations are building blocks that can be used for scale out architectures. For example, some TimesTen telecommunications customers with high throughput requirements, use application level partitioning to route transactions to a set of active standby pairs.

Scale Out using Active Standby Pairs with Exadata

Find out more about TimesTen In-Memory Database and TimesTen Application Tier Database Cache.

Disclaimer: these are my personal thoughts and do not represent Oracle's official viewpoint in any way, shape, or form.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.