Skip to content

Category

Engineering

GitHub’s post-CSP journey

GitHub’s post-CSP journey

Last year we shared some details on GitHub's CSP journey. A journey was a good way to describe it, as our usage of Content Security Policy (CSP) significantly changed from…

Patrick Toomey
An illustration of two octocats repairing a robot.

Moving persistent data out of Redis

Historically, we have used Redis in two ways at GitHub: We used it as an LRU cache to conveniently store the results of expensive computations over data originally persisted in…

Bryana Knight
An illustration of two octocats repairing a robot.

Orchestrator at GitHub

GitHub uses MySQL to store its metadata: Issues, Pull Requests, comments, organizations, notifications and so forth. While git repository data does not need MySQL to exist and persist, GitHub's service…

Shlomi Noach
An illustration of two octocats repairing a robot.

Introducing the GitHub Load Balancer

Over the last year we've developed our new load balancer, called GLB (GitHub Load Balancer). Today, and over the next few weeks, we will be sharing the design and releasing its components as open source software.

GitHub Engineering
An illustration of two octocats repairing a robot.

The GitHub GraphQL API

GitHub announced a public API one month after the site launched. We've evolved this platform through three versions, adhering to RFC standards and embracing new design patterns to provide a clear and consistent interface.

GitHub Engineering
An illustration of two octocats repairing a robot.

Building resilience in Spokes

Spokes is the replication system for the file servers where we store over 38 million Git repositories and over 36 million gists.It keeps at least three copies of every repository…

Patrick Reynolds