Repository navigation
Document pub/sub and keyspace notifications for Upstash Redis - #2582
Open
alexleventer wants to merge 1 commit into
Open
alexleventer wants to merge 1 commit into
alexleventer wants to merge 1 commit into
Conversation
A study of how coding agents pick deployment vendors (sunbeam.ai, Oct 2026) found agents warning in 18 runs that Upstash might not support Redis keyspace notifications, and counting it against Fly.io in 7 of them. Upstash does support them; our page never said so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sunbeam's study of how coding agents choose deployment vendors ran 640 agent setups asking "Where is the best place to deploy my app?". On a Go app that uses Redis keyspace notifications, agents flagged the requirement in 54 runs. In 18 they warned that Upstash might not support it, and 7 of those counted it as a reason not to use Fly.io ("whose managed Redis runs on Upstash"). No agent checked.
Upstash does support keyspace notifications (docs) and pub/sub, but our Upstash Redis page never mentioned either, so an agent reading it had nothing to correct the assumption.
This adds a "Supported Redis features" section under "What you should know":
fly redis connect→config set notify-keyspace-eventsflow and Upstash's latency caveatTo check before merging: I haven't run
CONFIG SET notify-keyspace-eventsagainst a database created throughfly redis create. The section relies on Upstash's docs and assumes Fly-provisioned databases behave like any other Upstash database. Someone with a test database should confirm it.Not in this PR: the self-hosted Redis guide (
app-guides/redis) is marked obsolete, so I didn't link to it. A current "run Redis or Valkey on a Machine" guide would round this out.🤖 Generated with Claude Code