Configuring overnight

GitHub began using Fastly to build a necessary new feature, and when their previous CDN provider experienced an outage, they moved much of their remaining content over to Fastly overnight. Because the Fastly service is truly self-provisioning and very quick to set up, GitHub was able to make the switch to Fastly and configure their service immediately - despite being in the midst of an attack and without having to engage a sales representative.

GitHub put Fastly in front of other services that were frequently subjected to DoS attacks. Using Fastly’s grace mode feature, they are able to limit the impact of an attack on end users by serving stale content from the cache instead of an error.

Improving speed & reliability

Prior to Fastly, GitHub Pages experienced consistently high performance loads when request spikes overwhelmed origin servers. In order to smooth out spikes and manage the viral nature of Pages, Fastly gave GitHub a dedicated IP address in each datacenter, which allows the hundreds of thousands of custom domains created with Pages to pass through Fastly. This accelerates the individual Pages websites and minimizes the requests to origin, making Pages faster and more reliable. In fact, according to this comparison, Pages beats Arvixe, Windows Azure, and Amazon AWS in terms of site-loading time.

Reducing origin server load

GitHub is also using Fastly to cache dynamic content, such as the raw rendered files from GitHub repositories. Before caching these files with Fastly, Raw.GitHub saw massive request spikes at constant intervals when thousands of machines requested user-generated content to perform automated actions. With Fastly in front of Raw, multiple requests for the same piece of content are collapsed to a single request, significantly reducing strain on origin.

Scaling for growth

For GitHub, Fastly has become a critical partner. GitHub has experienced rapid growth in recent years, and they relied on Fastly to help scale their services as they re-architected key components of their infrastructure. Using Fastly has allowed GitHub to focus capacity planning on their main site while continuing to support other popular services, such as Raw and Pages, without sacrificing performance.