This guide shows you how to keep your Redis-compatible caches in sync with your Postgres database in real-time using Sequin. By the end of this guide, you’ll have a working sink that automatically creates, updates, and deletes cache entries as your database changes, eliminating stale cache issues.

​
When to use this approach

This approach works well when:
  • You need real-time cache synchronization
  • You’re maintaining multiple caches across different regions
  • You can tolerate 100ms of latency (changes appear in cache shortly after database)
This approach is not a good fit if:
  • Your cache isn’t Redis-compatible. Instead, you should sink to a stream or queue destination and process the messages in your own system.
  • You need read-after-write consistency. In this case, you may want to write to the cache directly from your application.

​
Prerequisites

If you’re self-hosting Sequin, you’ll need:
  1. Sequin installed or a Sequin Cloud account
  2. A database connected to Sequin
  3. A Redis compatible cache (Redis, KeyDB, Dragonfly, Valkey etc.)

​
Create a Redis String sink

To get started, navigate to the “Sinks” page in the Sequin UI and click “Create Sink”. Select “Redis String” as the sink type. Configure the sink as follows:
1

Select the source

  1. Select your database from the connected databases list.
  2. Choose your table or schema containing the data you want to cache.
2

Apply filters

Keep all operations enabled (insert, update, delete) to maintain cache consistency.
If there are rows in the source table you don’t need to cache (for instance, rows that are only used for reporting or testing), you can apply a filter to exclude them.
3

Transform the data

Configure a transform function to store only the data you need in your cache:
def transform(_action, record, _changes, _metadata) do
  record  # Store the entire record
end
You can be more selective and only store certain fields in your cache:
def transform(_action, record, _changes, _metadata) do
  %{
    id: record.id,
    name: record.name,
    email: record.email
  }
end
4

Warm the cache with a backfill

To warm your cache with data currently in your source table, you can start the sink with an initial backfill.If you only need to warm your cache with a subset of your source table, skip this step for now and run an incremental backfill after the sink is running.
5

Group by primary key

by default, Sequin will group messages by primary key. This is a good default for most use cases as this will ensure every change to a specific row is processed in order.If you need to more specific message grouping, you can configure the sink to group messages by a different field.
6

Configure routing

By default, keys follow the pattern sequin:<table-name>:<primary-key>To customize keys, enable “Dynamic routing” and add a routing function:
def route(action, record, changes, metadata) do
  %{key: "#{metadata.table_name}:#{record.id}"}
end
This creates keys like users:123 instead of sequin:users:123.
7

Enter the connection details for your cache

Enter the configuration parameters for your cache.When maintaining a cache, you’ll typically want to keep the “Expires” value to 0 so that the cache entries never expire.
8

Create the sink

Give you sink a name and click “Create Sink”.

​
Verify your cache is being updated

If you specified a backfill, there should be messages in your sink ready for your system to process:
  1. On the sink overview page, click the “Messages” tab. You should see messages flowing to your sink.
  2. Query your cache to verify that the data is being updated: 
    GET sequin:users:1

​
Re-warming your cache

You may need to re-warm your cache in these scenarios:
  1. After infrastructure changes: Cache server upgrades/migrations
  2. Data model updates: Schema or business logic changes
  3. Cache eviction: Unexpected cache flushes
To do so, run a backfill. You can trigger a backfill manually in the Sequin Console or using the Sequin management API.

​
Next steps

You now have a cache that automatically stays in sync with your database. Changes to your Postgres data will appear in your cache within milliseconds, without any manual intervention or risk of stale data. Here are some helpful resources to bring this approach to production:

Connect your production database

Learn how to connect your production database to Sequin.

Deploy Sequin in production

Learn how to deploy Sequin in production.

Learn more about Redis String sinks

Learn more about how to configure your Redis String or Redis compatible sink.

Monitor your workflows

Learn how to monitor your system with Sequin’s built-in metrics.