Apache Cassandra vs. Riak

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Cassandra
Score 7.7 out of 10
N/A
Cassandra is a no-SQL database from Apache.N/A
Riak
Score 10.0 out of 10
N/A
Riak is a NoSQL database from Basho Technologies in Bellevue, Washington.N/A
Pricing
Apache CassandraRiak
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CassandraRiak
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache CassandraRiak
Considered Both Products
Cassandra
Chose Apache Cassandra
Four years ago, I needed to choose a web-scale database. Having used relational databases for years (PostgreSQL is my favorite), I needed something that could perform well at scale with no downtime. I considered VoltDB for its in-memory speed, but it's limited in scale. I …
Riak
Chose Riak
MongoDB seems to have copied a lot of functionality from Riak. This may be because MongoDB hired a number of former Basho engineers when Basho went bankrupt. That said, the new functions added to Riak after it became open source have successfully differentiated itself from Mongo…
Chose Riak
Riak is a key/value pair store which is great for certain use cases. For our use case, the ability to search is an extremely useful feature. Apache Cassandra can provide this while Riak cannot. Also again for our use case, the ability to delete is critical as we strive to …
Top Pros
Top Cons
Features
Apache CassandraRiak
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache Cassandra
8.0
5 Ratings
9% below category average
Riak
9.4
2 Ratings
7% above category average
Performance8.55 Ratings10.02 Ratings
Availability8.85 Ratings10.02 Ratings
Concurrency7.65 Ratings10.02 Ratings
Security8.05 Ratings6.02 Ratings
Scalability9.55 Ratings10.02 Ratings
Data model flexibility6.75 Ratings10.02 Ratings
Deployment model flexibility7.05 Ratings10.02 Ratings
Best Alternatives
Apache CassandraRiak
Small Businesses
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache CassandraRiak
Likelihood to Recommend
6.0
(16 ratings)
10.0
(6 ratings)
Likelihood to Renew
8.6
(16 ratings)
9.0
(5 ratings)
Usability
7.0
(1 ratings)
-
(0 ratings)
Support Rating
7.0
(1 ratings)
9.0
(1 ratings)
Implementation Rating
7.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apache CassandraRiak
Likelihood to Recommend
Apache
Apache Cassandra is a NoSQL database and well suited where you need highly available, linearly scalable, tunable consistency and high performance across varying workloads. It has worked well for our use cases, and I shared my experiences to use it effectively at the last Cassandra summit! http://bit.ly/1Ok56TK It is a NoSQL database, finally you can tune it to be strongly consistent and successfully use it as such. However those are not usual patterns, as you negotiate on latency. It works well if you require that. If your use case needs strongly consistent environments with semantics of a relational database or if the use case needs a data warehouse, or if you need NoSQL with ACID transactions, Apache Cassandra may not be the optimum choice.
Read full review
Basho Technologies
Riak is well suited to applications such as:
Transaction logging e.g. financial transactions and/or exchange rates.
Storing time series data, especially IoT.
Storing massive amounts of data e.g. corporation wide backups, data lakes etc.
A fully s3 compatible replacement for Amazon s3 ensuring data privacy.
Riak is not as well suited to:
Traditional RDBMS functions, especially those that join the outputs of one or more queries together to produce the desired result.
Read full review
Pros
Apache
  • Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
  • Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
  • Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
  • Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.
Read full review
Basho Technologies
  • Highly available: If nodes go offline for any reason, the system still operates.
  • Highly scalable: There is a minimum of 5 nodes, which can handle a lot by themselves. When scaling is required, it can be done easily, with minimal to no downtime on large scales.
  • Very fast searching: Riak has SOLR indexing built-into the core product, which makes querying for data very fast.
Read full review
Cons
Apache
  • Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
  • Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
  • There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.
Read full review
Basho Technologies
  • Deletes!!! We've seen on numerous occasions where Riak has "resurrected" deleted data. We've worked with Basho numerous times and tried multiple changes to the way we interact with Riak to prevent the problem but it still remains. The deletes seem to reappear weeks, even months, after the delete was issued. We've had to work around this issue by providing a "deleted" flag for all data objects stored in Riak. Thus, we do no delete but simply flip the flag. Excess baggage we would really like to not have to worry about.
  • Search. Currently there's no way to tell what data you have in Riak without already knowing a particular bucket/key. There is a way to list the keys for a given bucket but due to performance implications, this is not a viable method to lookup data. Especially when you have a large amount of keys in the bucket.
Read full review
Likelihood to Renew
Apache
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.
Read full review
Basho Technologies
Right now, I'm on a project where we need databases that can run on embedded systems. Riak isn't necessarily the best fit for that scenario. But when we need a clustered database, that's where we'd start considering Riak.
Read full review
Usability
Apache
It’s great tool but it can be complicated when it comes administration and maintenance.
Read full review
Basho Technologies
No answers on this topic
Support Rating
Apache
Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.
Read full review
Basho Technologies
Despite Basho going bankrupt and the project becoming fully open-source, community support is reasonably good, albeit a little slow at times. Paid enterprise-grade support is also available from former Basho engineers but the same company also contributes to the community support for free for basic questions or specific knowledge areas.
Read full review
Alternatives Considered
Apache
We evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for web and mobile applications due to its performance concern. Cassandra, by contrast, offers the availability and performance necessary for developing highly available applications. Furthermore, the Hadoop technology stack is typically deployed in a single location, while in the big international enterprise context, we demand the feasibility for deployment across countries and continents, hence finally we are favor of Cassandra
Read full review
Basho Technologies
Because of the RESTful HTTP interface, the consistency model, and because of the catalog-driven data model, Riak was an easy win over Redis and Memcached.
Read full review
Return on Investment
Apache
  • I have no experience with this but from the blogs and news what I believe is that in businesses where there is high demand for scalability, Cassandra is a good choice to go for.
  • Since it works on CQL, it is quite familiar with SQL in understanding therefore it does not prevent a new employee to start in learning and having the Cassandra experience at an industrial level.
Read full review
Basho Technologies
  • Riak has been a key part of our company's build process for our client's search backend. It is valuable for is in that it provides a reliable way to view the current search index.
Read full review
ScreenShots