DX-2962: add HTTP client section to effect-mq page

[CahidArda]

Summary

Follow-up to #790. Adds a "Connecting over HTTP" section showing how to run effect-mq's Redis store over the Upstash REST API with @upstash/redis instead of a TCP client, and explains when you'd want that: enqueueing from serverless/edge runtimes with no TCP, avoiding per-instance connections across many short-lived processes, and dropping the redis/platform peer dependencies.

No new storage driver is needed: effect-mq's store talks to Effect's client-agnostic Redis service, which only needs send and subscribe. The section provides a ~40-line UpstashRedis.layer built on @upstash/redis's exec and subscribe, then swaps it in for NodeRedis.

Changes

• redis/integrations/effect-mq.mdx: new "Connecting over HTTP" section between Usage and Billing Optimization — motivation, install, the UpstashRedis layer (TypeScript), usage with REST URL/token, note that HTTP and TCP clients can share a prefix, and a latency/throughput tradeoff note

Testing

• Adapter typechecks under strict (tsc, Effect 4.0.0-rc.112, effect-mq 0.7.0, @upstash/redis latest)
• Ran the page's full job flow (enqueue, delayed execute, worker, poll) through the adapter against a fresh start-redis database: same results and key layout as TCP
• Pub/sub wake-up verified over HTTP: worker with a 60s pollInterval handled a job 1.2s after a separate process enqueued it

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
upstash	🟢 Ready	View Preview	Aug 26, 2026, 10:28 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[linear-code]

DX-2962