4 ms·
I think its a strategic decision to use vercel for hosting and for example deno deploy or cloudfront for edge/lambdas to do frontend instead of using directly A
by exiguus 1y ago
I think its a strategic decision to use vercel for hosting and for example deno deploy or cloudfront for edge/lambdas to do frontend instead of using directly AWS. And have no backend or a backend everywhere else then on AWS.
The strategic behind it, is to avoid a dev/sec/cloud ops team that might cost yearly more then paying the 150-200% of costs that you have when you host it on AWS directly. But the 50-100% plus, will save you all the AWS terraforming, IAM, SecOP stuff. If you don't need SQS or a APIGateway etc., Vercel might be the way to go.
Talking about Next: Before there was only Angular with universal rendering that could do SSR / ISR. Second one was Next and den Nuxt. SSR or ISR is often a must have in enterprise projects. If it is not a internal app, you have todo SSR. And with a modern architecture, you decouple the frontend. So, no other options.
Recently we have also Remix, Astro and Svelte Kit for that. And the market get much more diverse, what i like.