Comparing two leading NoSQL databases
This post provides a brief technical comparison of Apache Cassandra and MongoDB. At Exponential.io, we use and like both databases so we’ll focus on what makes each unique and different.
Our view on databases is that a multi-database approach is often best. More often than not, using a single database results in using the wrong technology to address a given product need. In our experience, learning how to use each database for use cases that it addresses best is easier than trying to hack one database for all use cases (especially those that it’s particularly bad at).
To simplify a mult-database approach for other engineering layers, such as Platform Services and UX, we recommend the creation of a Data Services API. The Data Services API provides a standard REST API as the way for engineers outside of Data Services to query data without the need to know which database is used for persistence.
With that said, let’s get onto the comparison.
|Failover||Masterless, token ring||Master/slave|
|Secondary indexes||Sort of1||Yes|
|ORDER BY||Yes, via clustering columns||Yes|
|Update in place||No||Yes|
|Ease of setup||Easy||Easy|
|Fault tolerance||Exceptionally high||High|
|Schema||Yes, via CQL||Optional in client|
We specialize in helping professional developers, like you, expand your skill set. Our courses are focused on enabling you to learn everything necessary to use a new technology in a live, production application.
All courses are made with love in
Palo Alto, CA.
Subscribe to our newsletter