Cassandra Room for Improvement
One of the issues with the solution is that you cannot drop write like you're able to in MongoDB and MySQL, where you can join tables. Cassandra doesn't have joins between tables so you need other tools for that. You need to read all the data and put in memory and then add the joins. That is the area where I think they need improvement. Secondly, for example, when setting up your cursor, you have to be very sure about the read mechanism, because if you're not following the read mechanism and mistakenly build a key that is no longer unique then you start overriding data. There are a lot of improvements they could make including on the OS.
Software Engineer at Freelancer
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.View full review »
Senior Director IP led Services (PES) at a computer software company with 1,001-5,000 employees
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.View full review »
Managing Director at a tech services company with 1-10 employees
The interface could definitely be improved. It's a technical database and for me the features are not user friendly. I also think it's quite an expensive solution and I hope over time with more implementations, this will improve.
DevOps, Big-Data Architect at NetAngelS
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.View full review »