Valkey streams adapter
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
It seems Valkey is becoming a popular alternative to Redis. Are there any plans on providing an official Valkey adapter for Socket.io? Preferably based on streams, since that is more reliable and seems to be the recommended adapter when using Redis.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Socket.IO's existing Redis adapter and its streams-based implementation, then compare the compatibility requirements for Valkey. Done means an official Valkey adapter is defined and implemented with the requested streams approach, with its behavior validated against the project's adapter tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, redis, typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100