Cassandra Reviews

We are using this solution for IoT projects where there is a need for high-performance runtime databases.

Some of the valued features of this solution are it has good performance and failover.

The solution is not easy to use because it is a big database and you have to learn the interface. This is the case though in most of these solutions.

I have been using the solution for approximately one and a half years.

The stability of this solution has been good in my experience.

I have used Druid, Neo4j, and MongoDB previously.

The installation was not difficult. I have my DevOps team of six engineers that does the installation, maintenance, and everything else related to the solution.

We do the implementation of the solution.

I have also evaluated MongoDB and the performance of this solution is better. Additionally, I prefer this solution to MongoDB because when there is a lot of writing happening, MongoDB is better at reading. It is stable and a fantastic solution, but it does not mean that it fits everywhere.

When it comes to the ease of use of a solution it is not what matters, I do not look at it from this perspective. I am mostly concerned with the performance because as a developer and expert, we do not look at that easy of use we just want it to perform well. Even if it is a little bit complex, it is okay. The performance is the only thing I care about because if you are tech-savvy you should be good enough to write a code and use the function.

I would recommend this solution to others.

I rate Cassandra an eight out of ten.

Cassandra has some features that are more useful for specific use cases where you have time series where you have huge amounts of writes. That should be quick, but not specifically the reads. We needed to have quicker reads and writes and this is why we are using Cassandra right now.

The secondary index in Cassandra was a bit problematic and could be improved.

Cassandra can improve by having an ecosystem integrator that was more complete. For example, in some maintenance operations, we needed to deploy external tools to perform tasks that were not packaged alongside Cassandra.

I used Cassandra within the last 12 months.

Cassandra is a stable solution.

I have found Cassandra to be scalable.

I would recommend Cassandra for larger enterprises. It's not as useful for small or medium enterprises.

I have used other solutions similar to Cassandra, such as Couchbase.

The main differences between Cassandra and Couchbase are, Couchbase is more for general purposes, and it has a smaller latency. Whereas Cassandra is easier to manage with the open-source version in clusters environments.

The initial setup of Cassandra was simple. There is a large community that offered a lot of support.

We did not use professional support because it was not necessary. We found all the information we needed from the documentation.

Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise.

If you want technical support, you will need to pay for it.

I rate Cassandra a nine out of ten.

I was working for a client where there was a huge amount of data, where all the networks were intercepted. We used to do analytics on top of it. We did entity profiling. We take data and we use it to build profiles for users. Then we profile how many emails the user is sending. We see his complete profile and his behavioral traits, like what websites he's visiting and his e-commerce activity.

My client was looking into customer profiles and then doing analytics. I captured the data part and designed the schema. They would do an analysis from that data and would find out potential customers who would buy their product. They would find these things out and then project their marketing and sales to those customers.

The most valuable features are the counter features and the NoSQL schema.

It also has good scalability. You can scale Cassandra to any infinite level.

For my use case, it was more than sufficient. I used most of the features, whatever was available. I'm not sure what else can be improved.

We had very new data of almost 10 million people and it was very fast. We also found the scalability and performance side to be very good. It is stable and available. 

During the time it was not stabilized, there were maintenance requirements, but once it was stabilized, we did not have maintenance. Three people are required for maintenance. 

We use it very extensively. Almost a hundred people are using it.

We don't have any complaints about technical support. 

I have worked on GraphQL, MongoDB, and ActiveDays.

You cannot compare a MongoDB with Cassandra. They are very different because MongoDB is more document-oriented and Cassandra is a columnar database. You can compare it to Couchbase but comparing Couchbase to Cassandra is easy because Couchbase requires a lot of infrastructure to deploy and install it. 

We worked on complex scenarios, so the setup was complex. The Cassandra deployments were fine. The cluster and the profiling of the cluster did not take much time. We had some processes in place. It takes around half an hour to an hour. Fine-tuning was a bit of a challenge. 

It's a good tool and it's a growing tool. The support is good. I would definitely recommend it.

I would rate Cassandra a nine out of ten. Nothing is perfect but I believe that continuous improvements are coming.

We deploy this solution on-prem and on the cloud. I'm a senior data architect manager.

If you need availability and consistency, you can go with Cassandra. 

If you have a requirement of aggregation and joints, Cassandra doesn't support a solution that can give the aggregation. If they were to include these two areas, the aggregation and the complex joints, it would improve the solution a great deal. 

The solution is scalable. 

We now have a lot of regulatory compliance in the Middle East and they try to keep things local, including customer support. Most companies use the community version and not the enterprise solution.

The initial setup is generally straightforward and not overly complex. You can also look on Google and various YouTube clips for information on the setup. 

In the UAE or in the Gulf region, you're required to buy from a local vendor so prices will vary from vendor to vendor and region to region. We have a monthly license and you can generally bargain for a better price.

It's important to have a data architect or consultant on hand who knows the technology and can judge whether it's a suitable product for the use case. 

I rate this solution eight out of 10. 

Our primary use case for the solution is testing.

The stability of the solution and the documentation available can be improved. The solution is limited to a linear performance, which should be improved in the next release.

We have been using the solution for approximately one year and currently use version 4.11.

I rate the stability a six out of ten.

There is no customer service and support because it is an open-source tool.

The initial setup was difficult because the was no proper guide to assist with the installation process. Therefore, I rate the initial setup process as seven out of ten.

The application is open source, so we do not pay for it.

I rate the solution a six out of ten because I haven't found any consistency in its performance, which is not aligned with what we see on the back end. The solution is good, but its documentation can be improved.

• Log-structured storage
• CQL (Cassandra Structure Language)
• Ease of installation
• The node setup

This product is used as the storage facility for a very-high-throughput application, where a lot of NoSQL data is being captured and it needs to be processed.

The clustering needs to be better; it is getting there.

I have used it for four years.

Cassandra is stable thus far; the problems that I have encountered were with CQL and the JSON support in CQL.

The scalability is good, as long as you understand how to set up the nodes.

I did not have any interactions with technical support, because I was able to find answers to my questions online as I did my searches.

The other solutions that I have used have been the SQL engines but for this project, Cassandra was determined to be the better solution.

Setup was very straightforward.

Pricing and licensing depends on what you are doing: If you are using it for major production work, I recommend that you purchase the level of support that you would need.

This was the only product that was evaluated.

Learn how many nodes you are going to need and set up the right level of replication.

I designed a product catalog data model in Cassandra according to their features and properties, loading millions of data and performing the required queries over it. 

Now, I am getting much better performance than relational databases.

Here are some features which have been really helpful in my organisation:

• High Avaialability
• No downtime
• Better performance
• Greater scalability.

HA is one of the great features of Cassandra with no downtime, e.g., you can achieve continuous data without a single downtime because of node to node ring architecture.

Maybe they can improve their performance in data fetching from a high volume of data sets. 

I had to compare Cassandra with MongoDB. MongoDB is much better in data fetching than Cassandra.

We've used Cassandra in the past to design a right-node read-less ideology. We mainly use it for its database capabilities.

Right now, the solution is working very well.

Cassandra has a very good understanding of GBL, and how to cure GBL in time. The biggest problem is always with GBL in terms of understanding the drives' collector and making them work perfectly. Cassandra addresses this very well.

The solution's database capabilities are very good.

We actually find HBase to be faster and better than Cassandra.

The disc space is lacking. You need to free it up as you are working.

I have about ten years of experience working with the solution.

We have some experience with HBase, which we find to be a faster solution.

My first Cassandra project was with a project introduced to us by Facebook. That was ten years ago. There was a time I tried using it a couple of months ago, and I completed the project for Upwork for Cassandra. Right now, I have another project which is using a Cassandra cluster which is under my management. Previously, I had quite a big Cassandra cluster of about 100 nodes and about 500 terabytes of data.

Overall, I would rate the solution nine out of ten.