TrustRadius Insights for Apache Cassandra are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Greatest community and adoption: The Java-based NoSQL database has garnered a strong following with its greatest community and adoption. Many users have found it to be a highly popular choice among developers, benefiting from the extensive support and resources available.
Excellent integration with Apache Hadoop, Apache Spark, and Solr: Reviewers have consistently praised the database for its excellent integration capabilities with Apache Hadoop, Apache Spark, and Solr. This seamless integration provides a robust ecosystem of tools that enable efficient unit tests and stress testing.
Best-in-class performance across various workloads: Users have consistently highlighted the exceptional performance of this database across various read/write/mixed workloads. Its ability to provide low latency and high throughput has been widely appreciated by customers who require fast data retrieval and processing.
Loading Reviews List....
Cassandra Reviews
3 Reviews
Professional, Scientific, and Technical ServicesMarketing & Advertising3
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.
Pros
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)
Likelihood to Recommend
[Cassandra is well suited to] schema-less dataset for large key value stores.
Cassandra is the only database used by Algorithmic Ads. We use it for both real-time transactions and analytics. The primary application accessing Cassandra is a light-weight Java application that provides a RESTful web services API for all our other applications. The API is a focal point for integration and includes both business logic and data. The same API is used both internally and by our customers. We rely on Cassandra for its amazing performance, linear scalability, and continuous availability.
Pros
Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.
Cons
Cassandra is a poor choice for implementing application queues.
NoSQL requires thinking differently, and can be challenging for people with strong relational database backgrounds to understand. The CQL language helps with this, but it pays to understand how the engine works under the hood. That said, the benefits outweigh the challenge of the learning curve!
Database compactions and anti-entropy repair can be burdensome on a busy cluster. Significant improvements have been made in recent versions, but it remains as an operational challenge.
Likelihood to Recommend
Cassandra excels in a broad range of applications -- especially if you understand its data model and write your applications accordingly. It's an excellent choice for time-series data, and a poor choice for application queues. It performs the best if you can simply record history and compute from it, rather than going back and editing or deleting things a lot.
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.
Pros
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.
Likelihood to Recommend
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.
