PHPnews.io

Overview for 'githubengineering'




GitHub’s post-CSP journey

Written by GitHub Engineering / Original link on Jan. 18, 2017

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 our initial release nearly four years ago to where we ended up last year. It wasn’t until then that we felt our policy was rela…


Moving persistent data out of Redis

Written by GitHub Engineering / Original link on Jan. 9, 2017

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 Git repositories or MySQL. We call this transient Redis. We also enabled persistence, which gave us durability guarantees…


Orchestrator at GitHub

Written by GitHub Engineering / Original link on Dec. 7, 2016

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 does. Authentication, API, and the website itself all require the availability of our MySQL fleet…