Works well, good understanding of GBL and has good database capabilities
Pros and Cons
"The solution's database capabilities are very good."
"The disc space is lacking. You need to free it up as you are working."
What is our primary use case?
We've used Cassandra in the past to design a right-node read-less ideology. We mainly use it for its database capabilities.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have about ten years of experience working with the solution.
Which solution did I use previously and why did I switch?
We have some experience with HBase, which we find to be a faster solution.
What other advice do I have?
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.
Disclosure: I am a real user, and this review is based on my own experience and opinions.