This link has been bookmarked by 14 people . It was first bookmarked on 15 Nov 2009, by Alex Ko.
-
27 Sep 11
Jochen FrommFacebook’s architecture is based on typical hierarchical PHP Web application model with a layer of data caching and extracted services components. The caching layer is done via the stable and fast memcached open source software on top of one of the large
-
19 Jul 10
-
15 Jan 10
Nick GallPerhaps the most interesting and revealing aspect of Robert’s talk was the discussion of Facebook’s somewhat unique development process. At the surface it appears to have the contradictory goals of: minimizing down time, scaling fast, and extremely quick
via_delicious_20101217 continuousdeployment pinboardimport20141106
-
01 Jan 10
-
25 Nov 09
-
16 Nov 09
Kazuya Sakakiharaneed to think about training new developers; current developers have experienced the scaling, but newcomers have to face that huge scale from the beginning.
-
15 Nov 09
-
Facebook developers are encouraged to push code often and quickly. Pushes are never delayed and applied directly to parts of the infrastructure. The idea is to quickly find issues and their impacts on the rest of system and surely fixing any bugs that would result from these frequent small changes.
-
there is limited QA (quality assurance) teams at Facebook but lots of peer review of code
-
Another aspect of the Facebook engineering team is how large the ratio of active user to developer is. Currently it stands at 1.1 million users per developer. This is an attractive recruiting figure since every new Facebook engineer knows that they will have huge impact (positive or negative) quickly and thus this should keep the adrenaline high when pushing new features.
-
In the process, the Facebook team has also taken agility to the extreme and devised a set of principles, tools, and process improvements that allow their engineers to have quick and real impact
-
-
13 Nov 09
-
12 Nov 09
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.