Engineering

8 min

How we purge a cache in 150 ms across 310 cities

M

Meridian Engineering

From the network team

IN SHORT

Gossip, fan-out trees and one very fast fiber backbone. The path a purge takes from your API call to the last city.

A purge request lands in the closest city first. That city signs it and forwards it to four regional hubs over our private backbone.

Each hub fans out to the cities it owns. The slowest leg is usually Auckland, which is why we keep a hub in Sydney.

The result is a global purge that finishes before most users could reload the page.

Keep reading

All posts

Create a free website with Framer, the website builder loved by startups, designers and agencies.