wasm-workers-server VS readable-stream

"Wasm Workers Server (wws) is an open source tool to develop and run serverless applications server on top of WebAssembly. The applications are composed by multiple modules called workers. Each of these tiny modules is in charge of replying to a specific HTTP endpoint in your application." Wasm Workers Server, "JavaScript Workers based on JavaScript work out of the box with Wasm Workers Server. The server integrates a JavaScript interpreter compiled into a WebAssembly module. Currently, the interpreter we support is quickjs and we are working on adding new ones." JavaScript

Hey, dev here!

Here you have the GitHub and Documentation links:

- https://github.com/vmware-labs/wasm-workers-server/

- https://workers.wasmlabs.dev/

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