3 ms·
Next pushes towards serverless functions and API routes that I didn't really enjoy using for more than just a trivial endpoint. Blitz is currently built on top
by DenseComet 5y ago
Next pushes towards serverless functions and API routes that I didn't really enjoy using for more than just a trivial endpoint. Blitz is currently built on top of Next so this same issue came up, and its value proposition is really only there if you use Next.
I'm looking forward to this change and using Blitz again, as the frontend experience was super nice.
- leerob 5y ago> Next pushes towards serverless functions and API routes that I didn't really enjoy using for more than just a trivial endpoint. By default (through `next start`) Next.js uses a Node.js server. You don't need to use Next.js serverless: https://nextjs.org/docs/deployment#self-hosting https://nextjs.org/docs/deployment#self-hosting Most large applications don't use API Routes for large workloads. These teams likely have a completely separate backend/API, and Next.js is the connecting piece for their frontend. For smaller teams, or solo devs, it's more common to see their entire backend built with API Routes (most commonly used with something like Prisma): https://github.com/vercel/nextjs-subscription-payments https://github.com/vercel/nextjs-subscription-payments
- deleted 5y ago[deleted]
- DenseComet 5y agoI should've phrased it as all in on Next really. I really like Vercel and Next.js serverless for hosting, and I've usually put APIs on a subdomain. The issue is that then using Blitz for authentication and rpc layer becomes very hard to do.
- chrisweekly 5y agoHmm. IME, there are significant benefits to a BFF (Backend For Frontend), ie Next.js /api routes, even (or especially?) in the presence of a separate external API.