Replication across Amazon Regions using global datastores - Amazon ElastiCache for Redis
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Replication across Amazon Regions using global datastores

By using the Global Datastore for Redis feature, you can work with fully managed, fast, reliable, and secure replication across Amazon Regions. Using this feature, you can create cross-Region read replica clusters for ElastiCache for Redis to enable low-latency reads and disaster recovery across Amazon Regions.

In the following sections, you can find a description of how to work with global datastores.

Overview

Each global datastore is a collection of one or more clusters that replicate to one another.

A global datastore consists of the following:

  • Primary (active) cluster – A primary cluster accepts writes that are replicated to all clusters within the global datastore. A primary cluster also accepts read requests.

  • Secondary (passive) cluster – A secondary cluster only accepts read requests and replicates data updates from a primary cluster. A secondary cluster needs to be in a different Amazon Region than the primary cluster.

When you create a global datastore in ElastiCache, ElastiCache for Redis automatically replicates your data from the primary cluster to the secondary cluster. You choose the Amazon Region where the Redis data should be replicated and then create a secondary cluster in that Amazon Region. ElastiCache then sets up and manages automatic, asynchronous replication of data between the two clusters.

Using a global datastore for Redis provides the following advantages:

  • Geolocal performance – By setting up remote replica clusters in additional Amazon Regions and synchronizing your data between them, you can reduce latency of data access in that Amazon Region. A global datastore can help increase the responsiveness of your application by serving low-latency, geolocal reads across Amazon Regions.

  • Disaster recovery – If your primary cluster in a global datastore experiences degradation, you can promote a secondary cluster as your new primary cluster. You can do so by connecting to any Amazon Region that contains a secondary cluster.

The following diagram shows how global datastores can work.


            global datastore