From 942d53a857e8d62390518c5d3abff618a4ddb865 Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Wed, 10 Jun 2026 12:46:20 +0100 Subject: [PATCH] DOC-6738 removed mention of Active-active as a source DB --- content/embeds/rdi-when-to-use-dec-tree.md | 2 +- content/embeds/rdi-when-to-use.md | 1 - content/operate/rc/rdi/_index.md | 1 - 3 files changed, 1 insertion(+), 3 deletions(-) diff --git a/content/embeds/rdi-when-to-use-dec-tree.md b/content/embeds/rdi-when-to-use-dec-tree.md index 0dff786f12..f5219bef37 100644 --- a/content/embeds/rdi-when-to-use-dec-tree.md +++ b/content/embeds/rdi-when-to-use-dec-tree.md @@ -39,7 +39,7 @@ questions: text: | Are you transferring data from a single source database? whyAsk: | - RDI is designed to work with a single source database. Multiple sources or Active-Active replicas create conflicting change events. + RDI is designed to work with a single source database. Multiple sources create conflicting change events. answers: no: value: "No" diff --git a/content/embeds/rdi-when-to-use.md b/content/embeds/rdi-when-to-use.md index cec8ffa371..765df5d4ef 100644 --- a/content/embeds/rdi-when-to-use.md +++ b/content/embeds/rdi-when-to-use.md @@ -35,7 +35,6 @@ RDI is not a good fit when: - 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 data is ingested from two replicas of Active-Active at the same time. - 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. diff --git a/content/operate/rc/rdi/_index.md b/content/operate/rc/rdi/_index.md index 6b83d29319..8fff8c9c75 100644 --- a/content/operate/rc/rdi/_index.md +++ b/content/operate/rc/rdi/_index.md @@ -76,7 +76,6 @@ RDI is not a good fit when: - 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 data is ingested from two replicas of Active-Active at the same time. - 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.