Alternatives
Products that do what Resumable Web Streams does
Resumable streams to allow clients with flaky connections to reconnect to long-running streams like LLM responses. Uses Redis, but only needs O(1) commands per stream for the common case that resumption is not needed.
- 1AS
2012 · github.com
- 2

- 3HT
2016 · heartbeat.appbase.io
- 4

- 5

- 6

- 7

- 8

- 9

- 10

- 11

- 12

- 13RA
2016 · npmjs.com
- 14AR
2016 · github.com
- 15HA
2015 · github.com
- 16AR
2017 · github.com
- 17AS
2017 · github.com
- 18RU
2019 · github.com
- 19SC
2015 · github.com
- 20GR
Hey guys and gals! I'm learning Go at the moment and LOVING it. I was hoping to get constructive feedback on a project I'm working on - goatee - which is a notification server that utilizes Redis pub/sub and WebSockets. It's fairly bare-bones at the moment but I'm hoping to add in a lot more features as time goes on such as queueing and WebSocket channel subscriptions (via Go Socketio possibly).
2014 · github.com
- 21SL
2020 · systemflow.co
- 22ND
2018 · github.com
- 23OS
I built an open-source research agent. You ask a question, it searches the web via Tavily, synthesizes an answer with an LLM, and shows the sources it used. Answers stream in real-time. The interesting part is the backend. It's a single JS file (~100 lines) that handles web search, LLM streaming, and per-user conversation history. No vector database, no Redis, no separate storage service. It runs inside a cell — an isolated environment with a built-in database, search index, and filesystem. The cell handles persistence and streaming natively, so the agent code only has to deal with the…
Apr 2026 · github.com
- 24RA
2014 · reqr.es
Ranked by how close each launch is in meaning, then by votes. Refine with a description →