Sound effect
>>
Speaker: Now you're different than Google in the kinds of applications that you run. They're mostly running search queries, and you're running, you know, all kinds of queries and bringing back all kinds of data from the social graph, so how is it different in terms of the way that you build out your data center from the inside?
>>
Speaker: Google has a tremendous amount of information that they've indexed and archived and then present to users, but fundamentally, if you go to Google and you type in a search for tiger, and I go to Google and I type in a search for tiger, we're gonna see, generally, the same results. So they're presenting that same information to both of us. Facebook's a little different in that the context of our data is all social. So when you look at your friends and their status updates and their photos and the notes they may have written, you're going to see one set of date versus if I look at my friends and their photos and sort of their notes and their status updates. And those tend to be non-intersecting sets of data, so we have to present things very differently.
>>
Speaker: So it's much more dynamic in return.
>>
Speaker: Much more dynamic data set, and what that means is it's caused us to do a bunch of different things relative to caching and relative to federating all of that data up amongst thousands of different data bases. So that, as a user requests all of that sort of information, it's not -- we're not hitting one particular server every time for that -- for different data.
Sound effect
==== Transcribed by Automatic Sync Technologies ====
