@thedaviddelta
That's a very important question. SSR via edge functions are popular recently because I think there are valid reasons for those, like when you need dynamic server rendered HTML and having them on edge means they are fast for users...
@thedaviddelta However I think the costs should be more obvious, but I don't know on whose interests will displaying the costs fall: the framework or the deployment platform? Deployment platforms love it when we use up the budgets. Frameworks love it when we use their dependencies.
@ayo I've also noticed a CPU spike on my Raspbery Pi every time I post a link that's hosted there. I have a small amount of followers so the spike was never actually problematic though.
@anze3db yeah I think even a properly configured VPS could be enough, just the free-tier edge function budget on platforms like Netlify and Vercel gets used up quickly 😄 then they will put down the project
@ricard Yeah, I don't know how they do it... for me because a visit to an SSR page will trigger an edge function it quickly reaches the free tier budget, so not about load but more about the platform-enforced limit.
> "Posting an image on Mastodon causes hundreds or thousands of federated servers to fetch the preview details all at once, causing a high load for the target server and effectively creating the by now well-known "Mastodon DDoS" effect. For static websites this may not be much of an issue but it routinely brings down larger pages or those which have dynamic server-rendered content."
@ricard oh man, I wish they didn't promise quoted posts before... it made me stop thinking about how to implement it client-side because the API might change 😬
Add comment