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 Every Node in a Cassandra Cluster is the Same

An additional benefit — besides elasticity and fault tolerance — of having a single type of nodes in your cluster:

Having all nodes share the same role also streamlines operations and systems administrations tasks as well. Because Cassandra has a single node type, it has only a single set of requirements for hardware, for monitoring, and deployment.

As far as I can tell, Cassandra, Riak, Project Voldemort, Membase , and Terrastore[1] are the ones following this philosophy.


  1. Not 100% sure, so please correct me if I’m wrong. Update: Sergio Bossa clarified this in a comment.  ()

Original title and link: Why Every Node in a Cassandra Cluster is the Same (NoSQL databases © myNoSQL)

via: http://www.riptano.com/blog/spof-0-why-every-node-cassandra-cluster-same