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:
34 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)
