my nextjs serverless execution is through the roof. How can I make sure that it's cached properly? Serverless is looking like a scam right now, everytime someone access my api, the GB-Hrs go above the limit for no reason. can you please help me?
@@anton-shubin-live yeah that intuitively makes sense to me. Related structure you can also use a CDN for similar purpose altho I think that's more for static assets
Edge functions - serverless functions on CDN
This is what I needed to hear, thank you!
Cool
This explanation was perfect and exactly what I needed. Thank you! :)
Great to hear, thanks!
Wow that was concise. You deserve way more traffic.
Thanks!
Perfect explanation Tuomo. Thanks and subscribed
Great to hear thanks!
Great explanation, thanks!
Cheers!
Great explanation! Keep it up.
Thanks!
I understand now. Great explanation!
Cheers!
Very very very good video.
Thank you!
Thanks for the explanation
Cheers!
Thank you.
Cheers!
Now i finally understand.
That’s great!
my nextjs serverless execution is through the roof.
How can I make sure that it's cached properly? Serverless is looking like a scam right now, everytime someone access my api, the GB-Hrs go above the limit for no reason. can you please help me?
Here is more info on vercel's edge caching vercel.com/docs/concepts/functions/serverless-functions/edge-caching hope this helps!
Thank you
Cheers!
thank you
You're welcome!
Hey! Nice video! What about database access? If functions live on the edge, but you need SQL?
@@user-hh8fn5uo1u Do you then locate your Redis swarm on the edge as well, to make it sit close to your Edge functions?
@@anton-shubin-live yeah that intuitively makes sense to me. Related structure you can also use a CDN for similar purpose altho I think that's more for static assets
Thank you for a simple and comprehensive explanation 🫡