---
title: "Matteo Collina (@matteocollina) | Hashnode"
description: "Open Sourcerer, Node.js TSC member, Fastify Lead Maintainer. Read the latest articles by Matteo Collina on Hashnode."
url: "https://hashnode.com/@matteocollina"
---

@matteocollina

# Matteo Collina

@matteocollina · Joined June 2022

Open Sourcerer, Node.js TSC member, Fastify Lead Maintainer

## Comments

[Yes, the native fetch approach is compatible 100% with Next.js. No catch, no dependencies.](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8/comment/68b6f71e247042aa63186ea4#reply-68b702689e96f4ce75e7bbdc)

Reply · Article · Sep 2, 2025 · [Introducing Massimo](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8)

[PHP is essentially stateless. Each request clears its variable state in the VM.](https://hashnode.com/posts/seamlessly-blend-php-with-nodejs/6835db5e882cd1091e9c6da1/comment/68398c559ad06dcac56d5c4e#reply-683992bc4860772dbb8c2da7)

Reply · Article · May 30, 2025 · [Seamlessly Blend PHP with Node.js](https://hashnode.com/posts/seamlessly-blend-php-with-nodejs/6835db5e882cd1091e9c6da1)

[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..).](https://hashnode.com/posts/introducing-the-node-application-platform/66f2b953705b59e84cda2438/comment/67084d78abeba59e6e00b622#reply-6708be8cbbb54baad65b9909)

Reply · Article · Oct 11, 2024 · [Introducing the Node Application Platform](https://hashnode.com/posts/introducing-the-node-application-platform/66f2b953705b59e84cda2438)

[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) => { ... }).](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d/comment/669bc4c5e7c7f0d1d346a3c6#reply-66a2459182434a49dc324bcc)

Reply · Article · Jul 25, 2024 · [A guide to reading and writing Node.js streams](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d)

[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.](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d/comment/669bc4c5e7c7f0d1d346a3c6#reply-66a223b1f67fe113f8fcb4d2)

Reply · Article · Jul 25, 2024 · [A guide to reading and writing Node.js streams](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d)

[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.](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d/comment/6698f792d8d1c8446fa805d5#reply-66a2236196271f659e5801b5)

Reply · Article · Jul 25, 2024 · [A guide to reading and writing Node.js streams](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d)

[We have an amazing designer at platformatic :).](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d/comment/669b35d2ee40ae2f2205fd0b#reply-66a2223530807b6f84e024a3)

Reply · Article · Jul 25, 2024 · [A guide to reading and writing Node.js streams](https://hashnode.com/posts/a-guide-to-reading-and-writing-nodejs-streams/668fd751e5d695eed5680b4d)