MySQL to Redis
real-time replication
TwinCommit replicates MySQL to Redis in real time by reading the MySQL transaction log and applying every committed change exactly once and in commit order. Use it to keep a Redis cache exactly in sync with MySQL, with no triggers or capture tables on the source.
MySQL
log reader
commit-ordered · exactly-once
Redis
native writer
How capture works on MySQL
TwinCommit connects as a replica, reads the row-based binary log and tracks position by GTID, so failovers and replica promotions are seamless.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓GTID mode recommended
- ✓REPLICATION SLAVE and REPLICATION CLIENT grants
How apply works on Redis
Each row is written as a Redis hash (or JSON document) under a key template such as `orders:{ORDER_ID}`, with deletes removing the key. Optionally every change is also appended to a Redis Stream.
Requirements
- ✓A key template per table
- ✓ACL user with write access to the key prefix
- ✓TLS endpoint recommended
Setup
Set up MySQL → Redis in four steps
- 1
Prepare MySQL
Run twincommit check. It verifies binlog_format = row and binlog_row_image = full and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Redis
Add a target block for Redis. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: mysql
dsn: ${SOURCE_DSN}
server_id: 4201
target:
type: redis
url: rediss://cache.internal:6380
key_template: "{table}:{pk}"
format: hash
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MySQL to Redis replication FAQ
How does TwinCommit replicate MySQL to Redis?
+
TwinCommit reads changes from the MySQL transaction log, buffers them per transaction, and applies each committed transaction to Redis in commit order. Each row is written as a Redis hash (or JSON document) under a key template such as orders:{ORDER_ID}, with deletes removing the key. Optionally every change is also appended to a Redis Stream.
Does MySQL to Redis replication need triggers or capture tables?
+
No. TwinCommit reads the MySQL log directly and creates no objects in the source database.
Is MySQL to Redis replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Redis transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MySQL versions are supported?
+
MySQL 5.7, 8.0, 8.4, 9.x · Amazon RDS & Aurora MySQL · Azure Database for MySQL · Cloud SQL.
Use cases for this route
Related replication routes
Stream MySQL to Redis today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.