DOC-6026 page about when to use RDI #2505
Conversation
andy-stark-redis
requested review from
a team,
ZdravkoDonev-redis and
yaronp68
dwdougherty
left a comment
dwdougherty
left a comment
There was a problem hiding this comment.
Apart from one minor (non-)issue, LGTM.
Co-authored-by: David Dougherty <[email protected]>
| the source database, RDI automatically scales to a configurable number of processing units, | ||
| to fill the cache as fast as possible. | ||
|
|
||
| ## When to use RDI |
There was a problem hiding this comment.
I'm happy to do this myself, but I'd recommend also adding this section somewhere on this page: https://redis.io/docs/latest/operate/rc/databases/rdi/ - I think it would go great before the Data Pipeline Architecture section.
There was a problem hiding this comment.
@cmilesb Good idea! I don't mind doing it while I've got this PR open (it may need other changes anyway). Do you think a link to this page in the main RDI section is OK, or would you prefer to have an embed and use it in both the main section and in Cloud?
There was a problem hiding this comment.
@andy-stark-redis An embed is probably the better option. Thanks!
There was a problem hiding this comment.
@cmilesb The content has changed quite a bit now, but I've added all the new stuff in the Cloud page too, using an embed. Let me know what you think :-)
Added tocEmbedHeaders to the RC/RDI index file.
|
|
||
| Using RDI with Redis Cloud simplifies managing your data integration pipeline. No need to worry about hardware or underlying infrastructure, as Redis Cloud manages that for you. Creating the data flow from source to target is much easier, and there are validations in place to reduce errors. | ||
|
|
||
| ## Is RDI a good fit for my architecture? |
There was a problem hiding this comment.
I feel like adding the list info and the decision tree in the embed makes any page this embed is in way too long. Not sure if we really need the decision tree in every page the embed is in - I would think we could just embed this section and point to the when to use page for the details/decision tree. Unless there's some LLM-based reason not to?
There was a problem hiding this comment.
Totally agree - implemented.
The content for this is mainly taken from the existing RDI landing page, with a few small changes. The decision tree renders as a diagram in the page, but is mainly intended to help AI agents reason about the considerations when choosing RDI. If you think the visible diagram is annoying in the page then I can replace it with a "hidden" version that only the AI can see.