← Directory

Redis Connect PostgreSQL

Redis Connect PostgreSQL is an end-of-life connector that loads existing data and continuously replicates PostgreSQL change data into Redis Enterprise for…

  • Databases
Redis Connect PostgreSQL is an end-of-life connector that loads existing data and continuously replicates PostgreSQL change data into Redis Enterprise for real-time access.

Platform availability

Available on 0 of 6 install platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

57/100 Fair

Maintained
No data
Popular
No data
Easy to install
250 install platforms, install notes, Docker image
Light to run
100125 MB minimum RAM

Based on 2 of 4 factors.

How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

GitHub stars
50
Open issues
2
Last commit
2025-11-04
Latest release
v0.11.6-redis-connect-205
Activity
stale

Checked today - source: GitHub (redis-field-engineering/redis-connect-dist)

Resources & Compatibility

Minimum requirements: 125 MB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 11 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the Redis Python client In a terminal, run pip install redis to add the Python client that talks to Redis. Without this package, your app will fail with a missing-library error before it can connect. source
  • Start Redis and optional tracing Use the provided Docker Compose command to start Redis and the optional tracing collector. If Redis is not reachable, the app cannot read or write cache data, and ports 4317 (gRPC) and 4318 (HTTP) are for tracing if you enable it. source
  • Keep transaction keys in one slot If you use a Redis Cluster transaction (a group of commands that should run together), put the same tag in each key, like {tag}foo. That keeps the keys in the same slot so the cluster accepts the pipeline instead of rejecting it. source
  • End of life Redis Connect is end-of-life; critical fixes end 2026-05-31, and Redis Data Integration (RDI) is recommended for change-data-capture. source

Fetched today - each note links to its source

Alternatives (12)

  • Apache Cassandra
  • Azure Cosmos DB
  • CouchDB - Apache CouchDB is a document database that stores JSON data and speaks HTTP, with built-in replication, change tracking, and flexible views…
  • KeyDB - A Helm chart for KeyDB multimaster setup
  • MongoDB - MongoDB is a cross-platform, open-source document-oriented NoSQL database that stores data in flexible, JSON-like BSON documents instead of…
  • Redis - Redis is a fast, in-memory data structure store that can be used as a database, cache, and message broker.
  • Valkey - A Helm chart for running Valkey on Kubernetes.
  • apache-cassandra
  • apache-couchdb
  • cassandra - Apache Cassandra is an open source distributed database management system designed to handle large amounts of data across many servers, pro…
  • cockroach
  • couchdb-v2.x - Apache CouchDB is an open-source, document-oriented NoSQL database that stores data as JSON documents with a simple HTTP/JSON interface, bu…

Checked 9 days ago - source: AlternativeTo

Common questions

Can I replicate only selected PostgreSQL tables to Redis and map them to Redis data types?

Redis Data Integration can sync the PostgreSQL tables you choose to Redis and transform the data into any Redis data type without coding.

Why can a Docker Compose service reach Postgres but not Redis by hostname?

This can happen when the application connects to Postgres by service name but cannot reach Redis or Artemis using container hostnames. Check the Docker Compose networking between the containers.

How do I keep multiple keys in one Redis Cluster slot so a transaction or pipeline is accepted?

Add the same tag to each key, like {tag}foo, so the keys map to the same slot. That lets the cluster accept the pipeline instead of rejecting it.

Who is responsible for backups and restores if the PostgreSQL side is self-hosted?

You become fully responsible for backups, downtime, and patching when self-hosting PostgreSQL. Make sure you actually verify that you can restore from your backups.

Answers sourced from github.com, stackoverflow.com, stackoverflow.com, www.reddit.com

Community

Collected 5 days ago - public community threads