Mostly read-only, with ocassional writes when we update the database/CMS. The writes handled by a webhook which hits the Cloudflare worker upon any update. Workers is so fast, the data and website is updated in milliseconds. We use Vercel's on demand revalidation.
Honestly, the real revolution at Vercel with NextJs in my opinion is the ability to easily use Edge functions now in any NextJs project. It's strange to me how so few developers use this, and understand how powerful the Edge is with Cloudflare. Even at Vercel itself they are focusing on the App folder and React Server Components (RSC). But, if you store everything at Edge and use Edge functions, everything is so incredibly fast, and easy to hook up/maintain that all the tooling around RSC is entirely useless.
Well, edge functions have a really good case but costs have to be taken into consideration. We use them if the logic is unique to the app and access is minimal. Our backend handles the rest. This way we can control costs.
The Vercel $20 plan comes with a million edge function invocations. Are they really that expensive at scale vs all the maintenance you have to do for a traditional backend?
Honestly, the real revolution at Vercel with NextJs in my opinion is the ability to easily use Edge functions now in any NextJs project. It's strange to me how so few developers use this, and understand how powerful the Edge is with Cloudflare. Even at Vercel itself they are focusing on the App folder and React Server Components (RSC). But, if you store everything at Edge and use Edge functions, everything is so incredibly fast, and easy to hook up/maintain that all the tooling around RSC is entirely useless.