fastify-multipart VS benchmarks

As we mentioned earlier, the request payload (body) can be json or a form data, the form data type will be the one we use to upload files to the server, but we need first to add a package to handle this for use, therefore we"ll use fastify-multipart.

massive-wax upgrade -L -R -m 'test(/|\\).*\.js$' -t 'chore tap 15' -r repo-list -p ./tap-15.js -K Cloning https://github.com/fastify/fastify-multipart/ to fastify/fastify-multipart Cloning https://github.com/fastify/fastify-mysql/ to fastify/fastify-mysql Cloning https://github.com/fastify/light-my-request/ to fastify/light-my-request Walking C:\Users\behem\workspace\massive-wax\fastify\fastify-multipart Commit done for fastify-multipart Walking C:\Users\behem\workspace\massive-wax\fastify\fastify-mysql Commit done for fastify-mysql Walking C:\Users\behem\workspace\massive-wax\fastify\light-my-request Commit done for light-my-request Push done for fastify-multipart Push done for fastify-mysql Opened PR: https://github.com/fastify/fastify-multipart/pull/218 Opened PR: https://github.com/fastify/fastify-mysql/pull/50 Push done for light-my-request Opened PR: https://github.com/fastify/light-my-request/pull/129

We use a custom load-testing application to test the features of the Supabase platform. It consists of:

here is the github repo[0] with an app that helps me launch terraforms and k6 and keep track of launches/results

[0]https://github.com/supabase/benchmarks

We benchmark the various tools here: https://github.com/supabase/benchmarks

PostgREST is used inside every Supabase project. We have >50K projects now[0], some of them making (tens of) millions of API requests through PostgREST daily.

It's a fantastic piece of tech, especially when coupled with PostgreSQL Row Level Security. We have some benchmarks here in case you're concerned about performance: https://github.com/supabase/benchmarks/issues/2

[0] On our hosted platform. We don't add telemetry to self-hosting