News for hackers. Stuff that matters.
Re:Next.js 12 by letmeinhere on Tuesday October 26, 2021 @01:17PM (#29003177)
but (at least last I checked and from what I can glean from current docs) Vercel doesn't host databases, or integrate on a network level with the major cloud providers that do, so if you run your "back end" on Vercel you still need a "back back end" from a different provider and are opting into a huge amount of network operations burden to securely connect the two.
Re:Next.js 12 by gherkinnn on Tuesday October 26, 2021 @01:24PM (#29003265)
Welcome to the Jamstack.

/snark

I'd think of a Next-driven BE as a BE for FE. And since it's co-located, You can share types, validators, utilities, (mental) models, etc. across the same codebase.

A technique that does have its place. Not always. Maybe not even half the time. But cleverer people than me use it to some effect.

Re:Next.js 12 by sroussey on Tuesday October 26, 2021 @01:41PM (#29003517)
Check out supabase

https://supabase.io/

Re:Next.js 12 by rattlesnakedave on Tuesday October 26, 2021 @01:28PM (#29003316)
For this sort of thing I really like fauna (https://fauna.com/). I don't think you really "need" a "backend backend" anymore, and small dev teams are probably better off without them.
Re:Next.js 12 by chrisco255 on Tuesday October 26, 2021 @02:02PM (#29003858)
Right, they don't host the databases, but they do integrate with other database, etc. providers: https://vercel.com/integrations

Vercel itself I believe runs on a combination of Google Cloud and AWS.