Hacker News new | past | comments | ask | show | jobs | submit login
The Google technology stack (2008) (michaelnielsen.org)
68 points by erbdex on Jan 31, 2014 | hide | past | favorite | 14 comments




next time you should host youre site on appengine... :)


Maybe wordpress is to blame, but the poor man can still handle HN traffic. Did it recently [1]. Disclaimer: it's my blog.

[1]: http://idiallo.com/blog/2013/11/handling-1-million-web-reque...


+1 The HN effect.


Circa ~2005; correct me if I'm wrong but I don't think MapReduce has been used for search indexing at Google for half a decade.


It is more about the approach that keeps them there. i quote-

"Part of what makes Google such an amazing engine of innovation is their internal technology stack: a set of powerful proprietary technologies that makes it easy for Google developers to generate and process enormous quantities of data. According to a senior Microsoft developer who moved to Google, Googlers work and think at a higher level of abstraction than do developers at many other companies, including Microsoft: “Google uses Bayesian filtering the way Microsoft uses the if statement”


What replaced it?


Caffeine, based on the Percolator incremental processing framework: http://static.googleusercontent.com/media/research.google.co...


Thanks!


Google Caffeine was the public release. I don't believe the technical details have been published yet.


This is about a lecture that was going to be held in 2008. Can we update the HN subject line to reflect this?


Also Google's publications tend to run 3-4 years behind when the technology is actually developed. So this is actually describing the Google stack as it existed c. 2004.


3-4 years sounds like how long it takes for a new technology to be deployed as a major part of the stack


3-4 years after deployment. It takes time to understand how a technology will be used and for the details of it to stabilize.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: