Cassandra vs. MongoDB
Download as PPTX, PDF2 likes1,213 views
The document compares Cassandra and MongoDB across various dimensions including data model, indexing, availability, write scalability, query language support, performance benchmarks, ease of use, and aggregation capabilities. MongoDB is favored for rich data models and flexible indexing, while Cassandra excels in high availability and write scalability. Both databases have their strengths, making them suitable for different application needs.
Cassandra vs. MongoDB
- 2. Expressive Object Model MongoDB supports a rich and expressive object model. Objects can have properties and can be nested in one another (a.k.a. “object oriented”). Cassandra offers a fairly traditional table structure with rows, columns, and each column has a specific type. Verdict: If your problem domain needs a rich data model then MongoDB is a better fit for you. Cassandra vs. MongoDB
- 3. Secondary Indexes MongoDB – secondary indexes are first class constructs making it easy to index any property of an object stored in MongoDB even if it is nested. Cassandra – has only cursory support for secondary indexes. Good if you will mostly be going to be querying by the primary key. Verdict: If your application needs secondary indexes and needs flexibility in the query model then MongoDB is a better fit for you. Cassandra vs. MongoDB
- 4. High Availability MongoDB supports a “single master” model. Meaning master node + a number of slave nodes. Cassandra supports a “multiple master” model. The loss of a single node does not affect the ability of the cluster to take writes – so you can achieve 100% uptime for writes. Verdict: If you need 100% uptime Cassandra is a better fit for you. Cassandra vs. MongoDB
- 5. Write Scalability MongoDB with its “single master” model can take writes only on the primary. You can deploy multiple shards but essentially only 1/3 of your data nodes can take writes. Cassandra with its “multiple master” model can take writes on any server. The more servers you have in the cluster, the better it will scale. Verdict: If write scalability is your thing, Cassandra is a better fit for you. Cassandra vs. MongoDB
- 6. Query Language Support Cassandra supports the CQL query language which is very similar to SQL, but has limitations. MongoDB at this point has no support for a query language. The queries are structured as JSON fragments. Verdict: If you need query language support, Cassandra is the better fit for you. Cassandra vs. MongoDB
- 7. Performance Benchmarks – Database Model The database model/schema of the application being tested makes a big difference. Some schema’s are well suited for MongoDB and some are well suited for Cassandra. Cassandra vs. MongoDB
- 8. Performance Benchmarks – Load Characteristics In write-heavy benchmarks, Cassandra is expected to trump MongoDB. In read-heavy benchmarks, MongoDB and Cassandra should be similar in performance. Cassandra vs. MongoDB
- 9. Performance Benchmarks – Consistency Requirements Very often in a number of the ‘Marketing’ benchmarks the knobs are tuned to disadvantage the other side. Pay close attention to the consistency settings. Benchmark load may/may not reflect the performance of your application. So find a benchmark load that reflects the performance characteristics of your application. Cassandra vs. MongoDB
- 10. Easy of Use MongoDB is simple to get up and running. Cassandra has made strides and the adoption of CQL as the primary interface and it has taken this a step further making it simple for legions of SQL programmers to use Cassandra. Verdict: Both are fairly easy to use and ramp up. Cassandra vs. MongoDB
- 11. Native Aggregation MongoDB has a built in aggregation framework to run an ETL pipeline to transform the data stored in the database. Cassandra does not have a built-in aggregation framework. Cassandra vs. MongoDB
- 12. Performance Benchmarks – Consistency Requirements MongoDB you can choose to not enforce any schema on your documents. Each document in MongoDB can be a different structure and it is up to your application to interpret the data. Cassandra in the newer versions (with CQL as the default language) provides static typing. You need to define the type of very column upfront. Cassandra vs. MongoDB
- 13. Summary To summarize here are the important differences in table form: Cassandra vs. MongoDB
- 14. Sign Up for a free 30 day Trial Thanks for reading! Full article here Hosting & management for MongoDB® and Redis®. NoSQL management Simplified.