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

Why Membase Uses Erlang

On what makes Erlang one of the best environments for building distributed systems:

At the end of the day, the real question isn’t whether it would have been possible for us to implement our cluster management in another language; it’s really a question of effort and maintainability of the result. With any other environment, we would have had to reimplement at least part of what Erlang/OTP provides, while we haven’t really found ourselves reimplementing features provided by any other environment.

A NoSQL database per language ranking would look like:

  • C: 2 Redis, Tokyo Cabinet
  • C++: 3 Hypertable, MongoDB, Kyoto Cabinet
  • C#: 2 RavenDB, sones GraphDB
  • Erlang: 3 4 CouchDB, Membase, Riak, Hibari
  • Java: 8 Cassandra, Hadoop, HBase, OrientDB, Terrastore, Project Voldemort, Neo4j, Hypergraph

Original title and link: Why Membase Uses Erlang (NoSQL databases © myNoSQL)

via: http://blog.membase.com/why-membase-uses-erlang