Riak Reviews

10 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.0 out of 100

Do you work for this company? Manage this listing

Overall Rating

Reviewer's Company Size

Last Updated

By Topic




Job Type


Filtered By:

Reviews (1-5 of 5)

Adam Stern | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • 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.
  • When the index definition changes, reindexing takes an extremely long time.
  • Support (both paid and community based) is very very lacking.
  • It is expensive to run.
Read Adam Stern's full review
Gerald Chenvert | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • Riak is great at handling large volumes of requests. We've seen Riak perform well under large volume while keeping response times quite low.
  • Riak is also fast providing consistent sub 10ms reads in both the datacenter and cloud.
  • Flexible allowing storage of numerous data types. We heavily leverage this to store various JSON documents in a single bucket.
  • We really like the RESTful interface that is provided. Makes the learning curve almost invisible and provides a quick speed to market in using Riak.
  • 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 Gerald Chenvert's full review
Jared Holmberg | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • If you're considering a NoSQL solution, one of Riak's strengths is that it is built to scale with very low management overhead. Compare Riak to something like HBase (requires a full Hadoop cluster, along with YARN, and Zookeeper), and you'll find it's much easier to set up and maintain.
  • Schemaless design in Riak makes it really easy to apply whatever design you like. Since you're not locked into seeing things just the SQL way, you've got more freedom with the type of data you store and the way you store it.
  • Riak is highly reliable. It's built on a platform that's meant to be incredibly resistant to failure. If you run in Riak in a cluster or cloud based environment, you can trust that it will be very dependable.
  • At the time I was using Riak, data was stored as blobs so you couldn't query the data directly on the server. This has since been remedied with the addition of full-text search support.
Read Jared Holmberg's full review
Jeff Peck | TrustRadius Reviewer
December 11, 2015

My Riak Review

Score 9 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • Reliability -- we rarely have to do anything to maintain our Riak instance. It is just online and available for whatever we throw at it.
  • The Riak Python client is an excellent tool and handles parallel writes/reads very well
  • There is a large and very receptive community or Riak users and developers who seem to be able to help with most technical questions that have arisen.
  • It would be nice if there was a better way to configure Riak for multiple nodes with less manual configuration. Really, it's not a big deal, but I am being asked to write a "con" so this is what I thought of.
Read Jeff Peck's full review
Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • Consistency model is highly distributed, so uptime of our documents is always available.
  • Simple to use RESTful interface, which was easy to access from our Java application.
  • Data model using catalogs and indexes was simple, making it easy to store and retrieve our statements.
  • It does not have any native startup scripts in Linux.
  • Since it's built on Erlang, its a bit difficult to administer.
Read this authenticated review

Feature Scorecard Summary

Performance (1)
Availability (1)
Concurrency (1)
Security (1)
Scalability (1)
Data model flexibility (1)
Deployment model flexibility (1)

About Riak

Riak is a NoSQL database from Basho Technologies in Bellevue, Washington.

Riak Technical Details

Operating Systems: Unspecified
Mobile Application:No