Content
@
https://warpcast.com/~/channel/vercel
0 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
If Iâm understanding correctly, Vercel Fluid is all about persisting / reusing server VMs so a brand new one isnât spun up for every single request to a server function? Curious why this couldnât just have been the way Vercel worked from the beginning? @rauchg https://youtu.be/8a4_AAds0vU https://vercel.com/docs/functions/fluid-compute
3 replies
0 recast
8 reactions
rauchg
@rauchg
Itâs harder than it sounds. The naive way of doing it can also result in overloading the function instance and degrading performance. The very attractive thing about the 1:1 request to function model was a complete eradication of the ânoisy neighborâ problem that e.g.: VPSs suffer from. tl;DR: We focused on quality first then optimized.
1 reply
1 recast
6 reactions
JB Rubinovitz ââš-âš
@rubinovitz
My theory is that vercel heavily leverages Amazon lambda since it was conceived when serverless was very trendy. You canât persist servers on Amazon lambda.
0 reply
0 recast
3 reactions
typeof.eth đ”
@typeof.eth
Sometimes I feel like weâre doing a lot of work to avoid a server and a caching layer
0 reply
0 recast
2 reactions
