Redis Data Integration interactive demo

Deploy an RDI pipeline for a PostgreSQL database, follow inserts, updates, and deletes into Redis, and change a table's keys with a job file.

Redis Data Integration (RDI) keeps Redis in sync with a relational database, so your app and its agents read from Redis instead of the source. This demo follows a food delivery app that keeps its data in PostgreSQL. You deploy the pipeline, run SQL statements against the source, and see each change reach Redis.

The demo runs in your browser and doesn't connect to an RDI pipeline or a database. The configuration, job file, key names, and redis-di status output follow the RDI documentation. The data and timings are illustrative. The customers, restaurants, and orders are the same sample data as the Context Retriever interactive demo.

What the demo shows

  1. Initial sync. When you deploy a pipeline, RDI takes a snapshot of the tables you select and writes each row to Redis under its own key, as a hash or a JSON document.
  2. Change data capture. After the snapshot, RDI captures every insert, update, and delete committed to those tables and applies it to Redis, usually within a few seconds.
  3. Job files. A job file changes how RDI writes one table, such as its key pattern or its fields. A job only affects changes captured after you deploy it, until you reset the pipeline, and a reset doesn't delete the keys RDI wrote before.

Next steps

RATE THIS PAGE
Back to top ↑