Data Integration

Use Redis Data Integration with Redis Cloud.

Redis Cloud now supports Redis Data Integration (RDI), a fast and simple way to bring your data into Redis from other types of primary databases.

A relational database usually handles queries much more slowly than a Redis database. If your application uses a relational database and makes many more reads than writes (which is the typical case) then you can improve performance by using Redis as a cache to handle the read queries quickly. Redis Cloud uses ingest to help you offload all read queries from the application database to Redis automatically.

Using a data pipeline lets you have a cache that is always ready for queries. RDI Data pipelines ensure that any changes made to your primary database are captured in your Redis cache within a few seconds, preventing cache misses and stale data within the cache.

RDI helps Redis customers sync Redis Cloud with live data from their primary databases to:

• Meet the required speed and scale of read queries and provide an excellent and predictable user experience.
• Save resources and time when building pipelines and coding data transformations.
• Reduce the total cost of ownership by saving money on expensive database read replicas.

Using RDI with Redis Cloud simplifies managing your data integration pipeline. No need to worry about hardware or underlying infrastructure, as Redis Cloud manages that for you. Creating the data flow from source to target is much easier, and there are validations in place to reduce errors.

Is RDI a good fit for my architecture?

RDI is designed to support apps that must use a disk-based database as the system of record but must also be fast and scalable. This is a common requirement for mobile and web apps with a rapidly-growing number of users; the performance of the main database is fine at first but it will soon struggle to handle the increasing demand without a cache.

Use the information in the sections below to determine whether RDI is a good fit for your architecture. See also the decision tree for using RDI which presents the considerations in a straightforward question-and-answer format.

When to use RDI

RDI is a good fit when:

• You want your app/micro-services to read from Redis to scale reads at speed.
• You want to transfer data to Redis from one or more source databases.
• You must use a slow database as the system of record for the app.
• The app must always write its data to the slow database.
• Your app can tolerate eventual consistency of data in the Redis cache.
• You want a self-managed solution or AWS based solution.
• The source data changes frequently in small increments.
• The source database has no more than 20K changes per second.
• RDI throughput during full sync stays below 60K records per second, assuming an average record size of 1KB and a pipeline without transformations.
• RDI throughput during CDC stays below 20K records per second, assuming an average record size of 1KB and a pipeline without transformations.
• The total data size is no larger than 200GB, so a full sync completes in under an hour without exceeding the throughput limits above. RDI can ingest larger datasets, but it will take longer than an hour.
• You don’t need to perform join operations on the data from several tables into a nested Redis JSON object.
• RDI supports the data transformations you need for your app.
• Your data caching needs are too complex or demanding to implement and maintain yourself.
• Your database administrator has reviewed RDI's requirements for the source database and confirmed that they are acceptable.

When not to use RDI

RDI is not a good fit when:

• You are migrating an existing data set into Redis only once.
• Your app needs immediate cache consistency (or a hard limit on latency) rather than eventual consistency.
• You need transactional consistency between the source and target databases.
• The app must write data to the Redis cache, which then updates the source database (write-behind/write-through patterns).
• Your data set will only ever be small.
• Your data is updated by some batch or ETL process with long and large transactions - RDI will fail processing these changes.
• You need complex stream processing of data (aggregations, sliding window processing, complex custom logic).
• You need to write data to multiple targets from the same pipeline (Redis supports other ways to replicate data across Redis databases such as replicaOf).
• Your target Redis database is configured with Active-Active topology. Active-Active is not supported as an RDI Cloud target database.
• Your database administrator has rejected RDI's requirements for the source database.

Data pipeline architecture

An RDI data pipeline connects one or more source databases to one target Redis database. Sources can use the same or different supported database types. Each source has its own collector, connectivity, credentials, and selection of tables and columns. All sources share the pipeline's processor and target.

Each source first imports its selected data during the initial sync phase, then captures changes during the streaming phase. The pipeline transforms the captured records and writes them to Redis. You can monitor and manage each source from the pipeline dashboard.

RDI Cloud uses the Flink processor for all pipelines.

For more info on how RDI works, see RDI Architecture.

Pipeline security

Data pipelines are set up to ensure a high level of data security. Source database credentials and TLS secrets are stored in AWS secret manager and shared using the Kubernetes CSI driver for secrets. See Share source database credentials to learn how to share your source database credentials and TLS certificates with Redis Cloud.

Configure connectivity separately for each source. A source can use a public endpoint or AWS PrivateLink, subject to the source-specific requirements in Prerequisites. See Set up connectivity to learn how to connect your PrivateLink to the Redis Cloud VPC.

RDI encrypts all network connections with TLS. The pipeline will process data from the source database in-memory and write it to the target database using a TLS connection. There are no external connections to your data pipeline except from Redis Cloud management services.

Prerequisites

Before you can create a data pipeline, you must have:

• A Redis Cloud Pro database hosted on Amazon Web Services (AWS). This will be the target database.
• One or more supported source databases that are publicly accessible or hosted on an AWS EC2 instance, AWS RDS, or AWS Aurora:

Get started

To get started fast with RDI on Redis Cloud, see the RDI Cloud quick start to create a data pipeline between a PostgreSQL source database and a Redis Cloud target database.

To create a new data pipeline, you need to:

1. Create a Data Integration workspace for your Pro subscription.
2. Prepare each source database and any associated credentials.
3. Define the source connection and data pipeline by selecting which tables to sync.

Once your data pipeline is defined, you can view and edit it.

For complete production setups, including SQL Server failover handling, see Production use cases.

Billing and common questions

See the RDI Cloud FAQ for billing examples, reset and flush behavior, and working with multiple sources.

Maintenance windows

RDI Cloud maintenance follows the same subscription-wide maintenance window as your Redis Cloud Pro subscription. During a maintenance window, your data pipeline may experience brief interruptions as Redis applies updates.

To control when maintenance occurs, set a manual maintenance window for your Redis Cloud Pro subscription. Any maintenance window you configure applies to both your databases and your RDI data pipeline.