What *specific* software algorithms and design patterns make Google's queries so fast ?
`Background:` I know that Google's performance can (and often is) easily attributed to quality staff who love and do what they love, 
BUT strictly technically speaking, the following equation just makes no sense to me: Google **=** more data(actually huge amounts of data) **+** yet faster(??). I think it's logical and makes much more sense to me that it's the other way around: more data = slower .. however it looks like 
Google almost defies gravity and its not following the  conventional laws of physics when it comes to the performance of their [search service][1].
They seem to follow the irrational equation highlighted above (actually it looks like they just keep getting faster and faster as time goes on: the more data comes in the faster they get
and simply makes little sense to be able to juggle better with more balls then less balls - I can juggle pretty well with one ball but
with juggling with two balls is a great difficulty to me; yet if Google was me it would juggle better. IMO this is a bit odd to say the least). 



`Question:` What are the specific implementation paradigms (such as specific
programming algorithms implementation details, design patterns & overall solution architecture) that Google is implementing/employing that you and I aren't in our applications which enable Google to
make a remote application (namely Google's search service) often perform faster then our local applications ? 
As if to you and me 1+1=2 but to Google 1+1=3 - it almost makes no sense at all. 

What sets them(Google) apart ? What are the secret technical programming/design ingredients behind the bar-none performance of their implementation ? Please be as specific as possible.


`*Disclaimer*` General, widely available information on the subject such as the info found on [this thread][2] or [this one][3] or other popular and well-known know sources such as [Wikipedia][4] (even though very relevant) will not be considered as a valid answer candidate unless you provide arguments to support some new 'things' and insights like: new answers/facts/conclusions, new possibilities hypothesis- I am looking for software implementation details(not broad theories) which are little-know and you can't easily find while searching on Google (or other search engines) on the subject in question or cannot be found at all or is highly unlikely to find=not know by most developers; examples of acceptable answers can be: your personal opinion, a write up which which provides information which is generally not widely-known and/or is noticeably different in someway from widely available information. The widely available information can only be used as in the intro and/or outro of your answer but not as  the as the core argument (preferably it should not be in the core argument at all). Please post little-known and/or new technical info on the subject only. Thanks.


  [1]: http://googlefast.com/
  [2]: http://stackoverflow.com/questions/132359/how-can-google-be-so-fast
  [3]: http://stackoverflow.com/questions/1298860/how-does-google-serve-results-so-fast
  [4]: http://en.wikipedia.org/wiki/Google_platform
What *specific* software algorithms and design patterns make Google's queries so fast ?
===

`Background:` I know that Google's performance can (and often is) easily attributed to quality staff who love and do what they love, 
BUT strictly technically speaking, the following equation just makes no sense to me: Google **=** more data(actually huge amounts of data) **+** yet faster(??). I think it's logical and makes much more sense to me that it's the other way around: more data = slower .. however it looks like 
Google almost defies gravity and its not following the  conventional laws of physics when it comes to the performance of their [search service][1].
They seem to follow the irrational equation highlighted above (actually it looks like they just keep getting faster and faster as time goes on: the more data comes in the faster they get
and simply makes little sense to be able to juggle better with more balls then less balls - I can juggle pretty well with one ball but
with juggling with two balls is a great difficulty to me; yet if Google was me it would juggle better. IMO this is a bit odd to say the least). 



`Question:` What are the specific implementation paradigms (such as specific
programming algorithms implementation details, design patterns & overall solution architecture) that Google is implementing/employing that you and I aren't in our applications which enable Google to
make a remote application (namely Google's search service) often perform faster then our local applications ? 
As if to you and me 1+1=2 but to Google 1+1=3 - it almost makes no sense at all. 

What sets them(Google) apart ? What are the secret technical programming/design ingredients behind the bar-none performance of their implementation ? Please be as specific as possible.


`*Disclaimer*` General, widely available information on the subject such as the info found on [this thread][2] or [this one][3] or other popular and well-known know sources such as [Wikipedia][4] (even though very relevant) will not be considered as a valid answer candidate unless you provide arguments to support some new 'things' and insights like: new answers/facts/conclusions, new possibilities hypothesis- I am looking for software implementation details(not broad theories) which are little-know and you can't easily find while searching on Google (or other search engines) on the subject in question or cannot be found at all or is highly unlikely to find=not know by most developers; examples of acceptable answers can be: your personal opinion, a write up which which provides information which is generally not widely-known and/or is noticeably different in someway from widely available information. The widely available information can only be used as in the intro and/or outro of your answer but not as  the as the core argument (preferably it should not be in the core argument at all). Please post little-known and/or new technical info on the subject only. Thanks.


  [1]: http://googlefast.com/
  [2]: http://stackoverflow.com/questions/132359/how-can-google-be-so-fast
  [3]: http://stackoverflow.com/questions/1298860/how-does-google-serve-results-so-fast
  [4]: http://en.wikipedia.org/wiki/Google_platform