Full credit to the team who runs the Geonet website. For those who don’t know, it’s the website of the New Zealand crown research institute that handles all things seismic. Like many New Zealanders I’ve been to the website a lot since the recent Kaikoura Earthquake and I’ve never once experienced performance problems.
What I find particularly amazing is the scale they must be capable of handling. I imagine the normal website load is fairly light, perhaps in the order of a few hits per second. But following a major event like the earthquake, half of New Zealand, and I imagine a fair few others, are all over the website. I’ve got friends and family who talk about refreshing it every few minutes to see if that “really was an earthquake”. I’m guessing they’ve been handling tens or hundreds of thousands of hits per second in the last few weeks, maybe 4 orders of magnitude greater than usual.
I was interested to know what powers this (I’d hate to think my tax dollars were being wasted on resources that were mostly underutilized 🙂 ). Their blog indicates that they’re using Fastly which provides, in Fastly’s words, a “real-time CDN”. I imagine this event was a pretty good test of Fastly’s capability and Geonet’s integration, and from what I’ve seen, they performed very nicely.
Well done Geonet and Fastly.