DEV Community

Discussion on: How would you go about providing minimal-latency web experience for a single local event?

Collapse
 
saki7 profile image
Nana Sakisaka • Edited

This would create a faster experience, but everyone would still ultimately be going to Utah and back right? If your website could be edge-cached right at the event, how might we go about serving that HTML on-location somehow?

Yes. My original thoughts are basically a workaround for getting things faster while being minimally evil™.

You can do edge-caching for your local event if you build the original network like so, but you still need to take control of the local DNS server to point to that specific on-location cache.

I think you can't just do edge-caching (or on-site-caching) for websites where you don't have control to; that's a real evil stuff IMHO. If you really need to empower those external (yet specialized to your event) websites, I think the best way is to make a contract with their company and do the regular edge-caching as the event organizer.

EDIT: if you don't want to modify the network, why not change your domain's A & AAAA records to point to your local server machine at your event location, then make that machine an edge node for HTML caching?