Skip to main content
TrustRadius
Cassandra

Cassandra

Overview

What is Cassandra?

Cassandra is a no-SQL database from Apache.

Read more

Learn from top reviewers

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Cassandra?

Cassandra is a no-SQL database from Apache.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

82 people also want pricing

Alternatives Pricing

What is MongoDB?

MongoDB is an open source document-oriented database system. It is part of the NoSQL family of database systems. Instead of storing data in tables as is done in a "classical" relational database, MongoDB stores structured data as JSON-like documents with dynamic schemas (MongoDB calls the format…

What is HCL Zen Edge Data Management?

HCL Zen Edge Data Management (formerly Actian Zen) is a NoSQL and SQL (fully ANSI compliant) embedded database that runs on Windows, Linux, Android, iOS, macOS, in VMs and Containers with AES 256-bit encryption. Version footprints range from 5MB (client only) to 50 MB (embedded client-server) to…

Return to navigation

Product Demos

Presto and Cassandra: Doing SQL and Joins on Cassandra Tables

YouTube

CassandraDB Connector Demo | CassandraDB Integration

YouTube

Open Source BI Tools and Cassandra

YouTube

Spark and Cassandra: Doing SQL and Joins on Cassandra Tables

YouTube

Real-time IoT data analytics and visualization with Kaa, Apache Cassandra, and Apache Zeppelin

YouTube
Return to navigation

Features

NoSQL Databases

NoSQL databases are designed to be used across large distrusted systems. They are notably much more scalable and much faster and handling very large data loads than traditional relational databases.

8
Avg 8.8
Return to navigation

Product Details

Cassandra Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Cassandra is a no-SQL database from Apache.

Reviewers rate Scalability highest, with a score of 9.5.

The most common users of Cassandra are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-5 of 16)

review of cassandra

Rating: 6 out of 10
April 07, 2021
AA
Vetted Review
Verified User
Apache Cassandra
7 years of experience
Used for specific product (which is used by whole organization). Addressing for column store we need for uniqueness of proprietary information that Redis and Mongo does not support.
  • Masterless
  • Schema-less
  • Multiple datacenter usage w/ little or no data loss
Cons
  • Rebuild/repair of objects (tables) in the keyspaces, allow to ignore keyspaces to repair.
  • Monitoring tool form opscenter support for Cassandra 3.x (or some other open source tool)
  • UI browser type to view data (rather than csql)
[Cassandra is well suited to] schema-less dataset for large key value stores.

Cassandra Usage and Needs

Rating: 8 out of 10
September 27, 2017
RR
Vetted Review
Verified User
Apache Cassandra
4 years of experience
We are using Cassandra based on the requirements and data availability to the application (based on queries for search).
  • Cassandra lot of API's ready available for map reducing queries (like materialized queries).
  • Cassandra uses ring architecture approach, there is no master-slave approach (like HBase). If data is published on the node, the data will get synced with other nodes in the ring architecture, compared to HBase which has a dedicated master node to orchestrate the data into its slaves.
  • Write Speed
  • Multi Data Center Replication
  • Tunable Consistency
  • Integrates with JVM because it's written in Java
  • Cassandra Query Language is a subset of SQL query (less learning curve)
Cons
  • No Ad-Hoc Queries: Cassandra data storage layer is basically a key-value storage system. This means that you must "model" your data around the queries you want to surface, rather than around the structure of the data itself.
  • There are no aggregations queries available in Cassandra.
  • Not fit for transactional data.
Cassandra data storage layer is basically a key-value storage system. This means that you must model your data around the queries you want to surface, rather than around the structure of the data itself. This can lead to storing the data multiple times in different ways to be able to satisfy the requirements of your application.

What makes Cassandra different!!!!

Rating: 6 out of 10
June 07, 2016
Vetted Review
Verified User
Apache Cassandra
2 years of experience
I had used Cassandra in my academic projects which were related to cloud computing. I used it for a few projects on Salesforce where multi tenancy features are implemented. In such scenarios Cassandra was one the best choices for NoSql. Although we have used RDMS, the performance while using Cassandra was better.

I have simulated a few real time running apps like Facebook and Uber where I have used RDMS and Cassandra, and checked the performance using Jmeter. It clearly shows that Cassandra boosts the performance over RDMS. One thing I find difficult in Cassandra is following the documents, which are not so understandable.
  • Undoubtedly performance is an important reason
  • We have not encountered a single point of failure
  • Scalability of Cassandra is good which is the most important for the companies where demand is scaling day by day.
Cons
  • Cassandra has a wide range of asynchronous jobs and background tasks that are not scheduled by the client, the execution can be eccentric.
  • Because Cassandra is a key-value store, doing things like SUM, MIN, MAX, AVG and other aggregations are incredibly resource intensive if even possible to accomplish.
  • I think querying options for retrieving data is very limited.
Well Suited
Tunable Consistency
Write Speed

Less Appropriate
Ad-Hoc Queries
Unpredictable Performance

Cassandra Rocks !!!

Rating: 9 out of 10
October 16, 2015
KG
Vetted Review
Verified User
Apache Cassandra
3 years of experience
We used Cassandra to store personalization data of our customers so that we can have this information available through the cluster. The primary advantage of Cassandra is the cluster configuration so that there is not a single point of failure. The writes are faster when you want to write data into the storage. We used it for storing data in JSON format which is used to store anything in JSON format. The data was always up to date and there was less latency when we read from the system. I would highly recommend using Cassandra so as to make a system more scalable and process requests faster.
  • Cassandra is highly scalable.
  • It provides the flexibility to store data in any format. You can add column family dynamically as need by the application.
  • One of the best noSQL solutions I've used so far.
Cons
  • A better UI access for reading the data.
  • More graphical information to understand how the data is being processed, system uptime/downtime, etc.
  • I used Cassandra-cli for running quries but it is not very helpful when it returns a lot of results. If there was some way to improve the user queries, it would be great.
I think Cassandra is well suited when we want to store general data that is not really about banking transactions. There is a learning curve involved on how the data is stored and how it is processed.

Cassandra - pretty good if you know what you are doing

Rating: 8 out of 10
October 13, 2015
Vetted Review
Verified User
Apache Cassandra
3 years of experience
Cassandra is being used as a time series store for sensor data and is used by several researchers within our department.
It serves as the storage layer in our home grown sensor analytics platforms that utilizes spark for the computation. We use it to store billions of samples of wearable sensor data that is collected in various studies and experiments.
  • High Availability - we utilize the data replication features of Cassandra. This enables us to access our data even when several nodes have gone down
  • Data Locality - our architecture combines Cassandra storage nodes and computation nodes in the same machine. This enables us to utilize data locality and limit expensive network IO to read data.
  • Elasticity - Cassandra is a shared nothing architecture. Nodes can be added very easily and they discover the network topology. As soon as a node has joined the Cassandra ring, the data is redistributed among the existing nodes and streamed to it automatically.
Cons
  • Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
  • Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
  • There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.
Cassandra has excellent high availability and partition tolerance and has a robust architecture.
It is well suited for storing immutable data as deletes are extremely inefficient. As such, it is well suited for data archive and deep storage.
It is less appropriate for OLAP as has limited aggregation and filtering abilities, and no grouping whatsoever.
Return to navigation