readable-stream VS Redis

If it's a readable stream, you can just directly consume it with an async iterator: https://nodejs.org/api/stream.html#streams-compatibility-wit...

Node.js Stream

Note that the older Node.js streams API hasn't been deprecated or removed. It will co-exist with the new API, and it even provides a way to convert from a web stream and vice versa using the .fromWeb() and .toWeb() methods (both added in Node 17, although both methods still retain their experimental status).

Nodejs has piepes with its stream https://nodejs.org/api/stream.html

You then want what's invoked by that event to be consumed as a Response. NodeJS has something to replicate this with stream consumers where you can do all the response.text() you normally do.

[3] - https://github.com/nodejs/readable-stream/

First, we create a NodeJS ReadStream using fs.createWriteStream to open the test.log file in "append" mode. Then we start recursively looping using setTimeout. This simulates an application that logs text in the file at a variable rate. At each iteration:

This needs a comparison with streams, which is the standard way to achieve this in Node.js land.

https://nodejs.org/api/stream.html

One of the challenges Redis labs here have is that there's very little reason for their userbase to stay loyal to them.

antirez retired from Redis development a few years ago.

From https://github.com/redis/redis/graphs/contributors it looks like activity since he left has been mostly from people who didn't overlap with him much.

Redis Labs have not shown themselves to be outstanding stewards of the project as far as I can tell. Why shouldn't people support the fork?

Redis

Redis - real time data storage with different data structures in a cache

[0] https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md

Cache: a Redis cache