Apache Cassandra vs. DataStax Enterprise

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.

Incentivized

DataStax has a good scalable option with multiple clusters and a good write rate. Cassandra also is improving and is an open-source technology that has good community support. The UI is also easy to understand and implement required functions.

Incentivized

• 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.

Incentivized

• Datastax Cassandra provides high availability and good performance for a database. It is built on top of open source Apache Cassandra so you can always somewhat understand the internal functioning and why.
• Datastax Cassandra is fairly simple to start using, you can install/setup your cluster and be productive in 1 day.
• Datastax Cassandra provides a lot of good detailed documentation, and when starting, the detailed free videos on the Datastax site and documentation are very helpful.
• Datastax Enterprise Edition of Cassandra provides more tools, good support, and quick response SLA for enterprise business support.

Incentivized

• 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.

Incentivized

• Cassandra is a bit difficult to learn and understand
• The costs are slightly higher for our company
• Hardware requirement is moderate to high at the beginning

Incentivized

I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.

Incentivized

We will continue to use it because it scales well with commodity hardware and we are satisfied with the documentation and support.

Incentivized

It’s great tool but it can be complicated when it comes administration and maintenance.

Incentivized

There is a bit of a learning curve and tasks that are simple in traditional RDBMS systems can be complicated with DataStax Enterprise but once you get the hang of denormalizing data and getting the data model correct DataStax Enterprise is very usable. Usability from the developer's standpoint is very simple - the complication is on the architecture side with the data model.

Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.

Incentivized

We have had a few situations where we caused an outage or something has gone wrong and we are able to get a support person to offer live help within minutes. The escalation process is excellent - the best I've seen - and the support team is incredibly strong. Outside of emergencies, the team is very helpful with general questions and working through data model exercises and the subscription I believe still comes with some hours to help get the data model reviewed.

Apache Cassandra has the best of both worlds, it is a Java based NoSQL, linearly scalable, best in class
tunable performance across different workloads, fault tolerant, distributed, masterless, time series database. We have used both Apache HBase and MongoDB for some use cases which were within hadoop setup and JSON (JavaScript Object Notation) document store respectively, but given the overall factors favoring Apache Cassandra, it is a technology choice for multiple platforms!

Incentivized

I believe DataStax Enterprise is the best in class. There are some things that are different with the schema-less systems but I found DataStax Enterprise easiest to implement while evaluating. The replication is on par or better than others in practice. We are evaluating Astra in our test environment and that has additional benefits we are looking forward to using.

• The open source version of Cassandra is only suggested for learning the basic concepts and play with its core features. Unless you really want to invest a lot in your developers and architects knowing every detail of Cassandra, I prefer the DataStax enterprise version. Although the license cost is relatively high, I think they it is worth it. I'm thinking about the support, the monitoring tool OpsCenter, and the integration of Solr and Spark (for data analysis).
• Cassandra didn't fully replace our old and traditional relation database Oracle. In addition, it opens another door for us to deal with some special business use cases that NoSQL database can do better in a more feasible and efficient way.

Incentivized

• Highly Scalable Database, Highly Available Services, and Platforms.
• High Performance, Low Latency and Highest throughput across varying workloads.
• Configured, Tuned and Monitored correctly works to provide the best user experience!
• Negative: Maintenance and Debugging Corner Cases

Incentivized