What users are saying about
44 Ratings
Top Rated
63 Ratings
44 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.3 out of 101
Top Rated
63 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.3 out of 101

Add comparison

Likelihood to Recommend

Amazon Aurora

Many places where Aurora is well suited:
  • If you are trying to build a serverless backend.
  • Amazon hosted relational database service (RDS). So we do not have to manage the database maintenance.
  • Backup and archival can be done to AWS S3, which is very convenient.
  • It provides high performance and scalability.
  • It's very secure. You could use AWS Key management service (KMS) to encrypt and store data on AWS Aurora.
No photo available

Cassandra

Well SuitedTunable Consistency Write Speed Less AppropriateAd-Hoc Queries Unpredictable Performance
No photo available

Pros

  • The MySQL compatibility meant we didn't have to change anything in our system which used to run on a MySQL database. It was a very simple configuration change to point at the new instance once set up
  • Much better performance than our previous MySQL database (hosted on AWS RDS) for lower costs due to the way storage is managed
  • Storage management is much more simple as it grows and shrinks with you without having to allocate and deallocate storage to the database
Andrew Raines profile photo
  • Performant. In particular, write performance is very good. Recently, a lot of work to address the changing systems environment has been done to take advantage of areas like SSDs and very dense storage systems.
  • Distributed system logic. Multiple data centers and other common network configurations like heterogeneous nodes are handled and exploited well.
  • Community. Strong community with users and project contributors worldwide. The open-source and commercial software people work well together with sharing of lessons learned and improvements based on feedback.
Gary Ogasawara profile photo

Cons

  • Without direct access to the instances it isn't possible to do a few things you'd be able to do if you were running your own database server, but this is rarely an issue
Andrew Raines profile photo
  • Managing the big cluster of Cassandra , even with the DataStax Enterprise Version, is still quite challenging for a maintenance team, considering the frequent version upgrade (even in the rolling fashion) and more frequent auto-repair, for me on this area, a powerful tool should be provided to "automate" this process as much as possible.
  • The TTL design is good, however the pain is if the TTL is set on some data already inserted, it can not be simply updated. Unless that data is reinserted again, this fact causes a lot of issues in case the business strategy is changed which requires the purge strategy to be updated also.
  • As the nature of Cassandra is still Java based, the GC sometimes eats some performance, if Cassandra can allow using more non-Heap memory space, to reduce the GC efforts which will free more power on the hardware.
  • The default indexing strategy for JSON formatted data in the DataStax's Solr integration is not available. At this moment we have to implement our own to support our JSON text stored. We extract the key field from our data which might be required to be ad-hoc searched, converting them into the JSON format (only one level Map), and save them into the Cassandra column. On top of that we want Solr to index the key of each token.
yixiang Shan profile photo

Likelihood to Renew

No score
No answers yet
No answers on this topic
Cassandra8.0
Based on 11 answers
In our POC Cassandra satisfies all our needs and expectations. We would like to do an additional POC to test its cross-continent cluster level replication features, measuring the performance and data consistency level to help us finally decide how to move to production.
yixiang Shan profile photo

Alternatives Considered

Using cloud-based services such as RDS or Aurora take all the hassle out of managing database servers yourself. It also gives you the flexibility to easily spin up and down additional instances and as when required. Where Aurora outshines RDS is in terms of performance - we saw around 2-5x improvement in query read times across the board.
Andrew Raines profile photo
Technology selection should be done based on the need and not based on buzz words in the market (google searching). If your data need flat file approach and more searchable based on index and partition keys, then it's better to go for Cassandra. Cassandra is a better choice compared with HBase because Cassandra has a lot of API's ready and available for map reducing queries (like materialized queries). Cassandra uses ring architecture approach, there is no master-slave approach (like HBase). If data published on of the node the data will get synced with other nodes in the ring architecture when compared to HBase which has a dedicated master node to orchestrate the data into its slaves.
Ravi Reddy profile photo

Return on Investment

  • The main positive for my team is the time that has been freed up from the tasks of managing updates and fixing replication issues.
  • A negative for myself as a database administrator is removal of features that were available in Mysql. Examples include 1) the use of the storage engines other than InnoDB (such as the Federated Storage Engine), 2) certain administrative privileges such as ability to export to csv file and easy ability to kill processes. I seem to also forget they removed the built-in kill ability and you must use their own provided kill functionality.
No photo available
  • 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.
yixiang Shan profile photo

Pricing Details

Amazon Aurora

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

Cassandra

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details