News for hackers. Stuff that matters.

A comment on Vercel Serverless Functions vs. Cloudflare Workers. Parent comment

Re:Vercel Serverless Functions vs. Cloudflare Workers by silviogutierrez on Thursday March 25, 2021 @07:21PM (#26586912)
I wonder this too, given ultimately, 99% of non-static sites will need to reach out to a central database. So to render a dynamic page, your worker then has to go to the DB, no?

Curious what is the use case. You can cache stuff, as detailed in the post, but assuming you have huge variance in page contents per user, I can't see too much use. I must be missing something.

[ Parent | on HN ]
Re:Vercel Serverless Functions vs. Cloudflare Workers by zizee on Thursday March 25, 2021 @08:23PM (#26587442)
A lot of applications are read heavy on their database. When this is the case, you can make reads to a read only slave closer to the edge. There are other options, but depending on your applications architecture this might be a relatively easy way to reduce latency on a large portion of your traffic.
[ Parent | on HN ]
Re:Vercel Serverless Functions vs. Cloudflare Workers by sssilver on Thursday March 25, 2021 @09:19PM (#26587822)
Why not use a database with a worker?

https://www.cloudflare.com/products/workers-kv/

[ Parent | on HN ]
Re:Vercel Serverless Functions vs. Cloudflare Workers by MuffinFlavored on Thursday March 25, 2021 @10:43PM (#26588269)
Key/value store doesn't really have joins, aggregation, tables, references, etc.
[ Parent | on HN ]