From ac6b6ab91a80095a8fed6c6c357ded2f7faf6e61 Mon Sep 17 00:00:00 2001 From: Sam Ruby Date: Thu, 15 Aug 2024 03:35:47 -0400 Subject: [PATCH] mention caching as a potential use case for Redis --- happy-path/redis.html.markerb | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/happy-path/redis.html.markerb b/happy-path/redis.html.markerb index c5f890beed..5c68cff45e 100644 --- a/happy-path/redis.html.markerb +++ b/happy-path/redis.html.markerb @@ -7,6 +7,10 @@ order: 7 [Upstash Redis](https://fly.io/docs/reference/redis/) is used by this application for its [pubsub](https://redis.io/docs/latest/commands/?group=pubsub) capabilities, but it can do [so much more](https://upstash.com/docs/redis/overall/rediscompatibility). +In particular, Redis is useful for caching: +[Node](https://redis.io/learn/develop/node/nodecrashcourse/caching), +[Rails](https://guides.rubyonrails.org/caching_with_rails.html#activesupport-cache-rediscachestore). + In this application, updates are broadcast to all machines via Redis, and then each machine informs browser clients of the update via [WebSockets](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API). Client the request -updated information from the application using HTTP GET. \ No newline at end of file +updated information from the application using HTTP GET.