How We Made GitHub Fast

Simon Willison - Simon Willison - October 22, 2009

How We Made GitHub Fast. Detailed overview of the new GitHub architecture. It’s a lot more complicated than I would have expected—lots of moving parts are involved in ensuring they can scale horizontally when they need to. Interesting components include nginx, Unicorn, Rails, DRBD, HAProxy, Redis, Erlang, memcached, SSH, git and a bunch of interesting new open source projects produced by the GitHub team such as BERT/Ernie and ProxyMachine.



Categories: Blogs  Simon Willison  

Comments

anonymous avatar

The only disadvantage to this strategy is that the inner SSH is needlessly encumbered by the cost of encryption/decryption when none is stringently necessary. It’s possible we may change this this inner SSH contact with something more efficient. phlebotomy

Posted by jony on 02 Feb 2012 at 19:58



 
anonymous avatar

The tasks layer serves to tie together any non business logic from a variety of third party services or persistence technologies. While setup and defining a service such as twitter would occur in the infrastructure layer, executing and combining the results with, say, a local NHibernate database, would occur in the tasks layer. Thanks.
Regards,
Personal statement accounting

Posted by jafffa on 04 Feb 2012 at 07:20



 
anonymous avatar

Its goal is to enable you to develop projects much faster than you could if you were writing code from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and logical structure to access these libraries. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task. Thanks for sharing.
Paradise Valley Homes

Posted by santa on 04 Feb 2012 at 10:26



 


Add comment

Name:

Email:

URL:

Smileys

Remember my personal information

Notify me of follow-up comments?