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



How Does YARN (NextGen MapReduce) and Mesos Compare?

Jay Kreps (LinkedIn) provides an excellent response to the question in the title on a Quora thread:

  1. Java vs C++
  2. Memory scheduling vs both memory and CPU scheduling
  3. Unix processes vs Linux container groups
  4. Pull vs push resource request model
  5. 3x more code in YARN
  6. YARN integrated pluggable schedulers vs Mesos’ upcoming hierarchical scheduling
  7. YARN integrates with Kerberos and inherits Hadoop security
  8. YARN provides rach and machine locality out of the box vs Mesos allowing to implement these
  9. YARN is still under work vs Mesos being a mature project
  10. YARN is the next generation of Hadoop MapReduce so you’ll be able to use on your Hadoop cluster
  11. YARN is written by Yahoo/HortonWorks which has shown to be experienced with multi-tenancy and very large-scale cluster computing. But YARN still needs work and testing.
  12. Mesos ships with a number of out-of-the-box frameworks.

You can find out more about Mesos here and about YARN here. And if you have a Quora account go upvote Jay’s answer.

Original title and link: How Does YARN (NextGen MapReduce) and Mesos Compare? (NoSQL database©myNoSQL)