[quicksnap]

I've been working with Next for a couple of weeks, here's my take:

- Next.js aims for "pit of success" in building sites with React that are optimized for CDNs and small builds

- Deploying said sites to Vercel takes advantage of the CDNs, so most of the users are getting cached data.

So, for this site, I would assume:

- There is no backend - All the HTML is cached and contains a static generation of the page(s)

- The javascript is also cached

- Vercel CDN is fast.

That's it!

[tomglynch]

Would it being cached mean that when the ship became unstuck, and the website changed from 'Yes' to 'Sort Of' or to 'No', that people who were checking back would receive an incorrect cached version?

[noahtallen]

The new copy is pushed to the CDN pretty quickly. I don’t know much about vercel. But the benefit of CDNs is that there is a 1:N relationship between you and the edge servers, and then an N:M relationship from the edge servers to the users.

So there are a lot more servers much closer to people using your site. Pushing a new copy from “you” to each edge server is pretty straightforward. I imagine Vercel does it pretty quickly, but sometimes the edge server could poll for changes maybe once a minute, which is pretty cheap to do.