Yes, the native fetch approach is compatible 100% with Next.js. No catch, no dependencies.

PHP is essentially stateless. Each request clears its variable state in the VM.

Our OSS application server is written (mostly) in JS because we upstreamed all our improvement to Node.js core over the last few years, so everyone can enjoy them. Our goal is to advance the commons too. It also massively simplify distribution and onboarding, as it’s just a Node.js script. In terms of functionality, Watt allows you to run your Node.js application as-is with all the benefits listed above. Specifically, our application server provides additional capabilities to all frontend frameworks (Astro, Next, Remix, etc..).

Stasa Stanisic you can just call reply.send(stream) or return stream in your Fastify route. Using barebone HTTP, you should do pipeline(a, b, c, res, (err) => { ... }) .

use @fastify/static :). Don't stream files directly because there are infinite edge cases that will inevitably result in a security issues in your server.

Good spot! The buffer is flushed on first write. Because the cb will be called after an event loop turn (it's async!), we need to wait for drain . To counteract this effect there are cork() and uncork(). They are used to send out the http headers for example.

We have an amazing designer at platformatic :).