throttle

[Uzlopak]

Checklist

• [ ] run npm run test and npm run benchmark
• [ ] tests and/or benchmarks are included
• [ ] documentation is changed or added
• [ ] commit message and code follows the Developer's Certification of Origin and the Code of conduct

[Uzlopak]

You should use pipeline instead, .pipe does not add error handling.

Ok, I will use pipeline

Note that using an intermediate stream adds significant overhead.

Should I put that into the readme? Or is there a different approach, that I am not aware of?

I actually wanted to write about the feature for the blog of @Eomm

https://github.com/Uzlopak/blog/blob/main/case.md

[Uzlopak]

@mcollina

Do you think it makes sense to create a new package called @fastify/throttle?

[Uzlopak]

I am actually working on the distributed part.

see https://github.com/Uzlopak/blog/blob/main/case.md#throttlegroups

also yes, i initially wanted to just handle streams. Maybe make it optional to handle also buffer and strings if an option is set (opt-in)

[Uzlopak]

Created a new repo fastify/throttle and will do the changes there.