search

tastejs / nuxt-movies

Nuxt.js Movies - a TMDB client optimized for Core Web Vitals
https://nuxt-movies.vercel.app/
73 stars 24 forks source link

Hosting #2

Closed addyosmani closed 3 years ago

addyosmani commented 3 years ago

Perhaps it would be interesting to get a sense of where most Nuxt.js users are hosting their deployments so that are aren't picking a hosting environment that's overly slow or overly optimal. Some of the candidates for hosting I have in mind are Netlify or Vercel, but I'm very open to whatever we think makes the most sense here.

pi0 commented 3 years ago

We have two options of deployment:

I think for purpose of CWV, it shouldn't matter since TTFB for a cached lambda or prerendered version is almost the same (depending on CDN)

For choosing serverless, nuxt is platform agnostic meaning we can choose between Vercel, Netlify, Cloudflare workers and azure with same project (see this demo). Cloudflare workers is probably most otimimal target both for CDN and coldstart-wise but an experimental target and is not generic. Deploying on netlify has close results of vercel with only downside that we loose SWR caching since it is not supported ATM by them.

In conclusion, I would suggest going with Vercel serverless target.

addyosmani commented 3 years ago

Thank you, @pi0! This background information is very helpful. I would be comfortable going with your suggestion of using Vercel with serverless target for hosting here.

anton-karlovskiy commented 3 years ago

@addyosmani I used Vercel and Netlify for the movies Next.js project. I'd like for us to use Vercel too since we can keep the hash URL at a specific point. Of course, we can keep the hash URL with Netlify but measuring performance on the Netlify hash URL keeps throwing errors, which is not the case in Vercel. I'm afraid I have not dug into it so do not have a clear reason.

addyosmani commented 3 years ago

Thank you, @anton-karlovskiy. I am quite comfortable with us using Vercel for the reasons mentioned on this thread. Perhaps once we have the initial code landed in this repo for the port, I can setup a shared Vercel account between the Nuxt.js teams and us and that way everyone has access? In the mean time I think it's perfectly fine for folks to be using their own Vercel deploys/accounts to get something up and running.

anton-karlovskiy commented 3 years ago

@addyosmani @pi0 I think we can close this issue.

addyosmani commented 3 years ago

sgtm