ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

hardward: All content tagged as hardward in NoSQL databases and polyglot persistence

Facebook: From Function-Based to Resource-Based Servers With the Disaggregated Rack

Most of the servers are configured depending on the functionality they’ll provide: here are the web servers, here were the cache servers, and these are the database servers. Facebook has been using the same approach, but according to Mark Hackman’s post: “How Facebook Will Power Graph Search“, they’ll start looking into having resource-based racks: here’s the compute power, here’s the RAM, and here’s the storage. If you think about it, this is exactly how Amazon has structured their cloud infrastructure services.

Original title and link: Facebook: From Function-Based to Resource-Based Servers With the Disaggregated Rack (NoSQL database©myNoSQL)

via: http://slashdot.org/topic/datacenter/how-facebook-will-power-graph-search/