Riak performs well as a statement document store
Updated June 17, 2016

Riak performs well as a statement document store

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Riak

It is being used as a backend for a web application used for storage of generated daily merchant statements.

Pros

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

Cons

  • It does not have any native startup scripts in Linux.
  • Since it's built on Erlang, its a bit difficult to administer.
  • Riak has positively allowed us to store our documents with high availability and redundancy.
  • Riak has made troubleshooting our application easy by using RESTful URLs to identify where data may be inconsistent.
  • Riak performs well under high load.
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.
Riak met all the requirements needed for a scalable, available, consistent statement store.
Riak is well suited for storing documents using a RESTful URL, such as files in byte format. I would not recommend using it for structured data with many relations.

Using Riak

10 - Riak is primarily used for document store via its RESTful interface.
4 - The primary support case for Riak is for datastore design as well as replication management and migrations.
  • Document store for reports.
  • Key value store.
  • High availability.
  • We have been considering using Riak as a hierarchical key value store for configuration purposes.
  • Additional reports servers, and transaction data store for BI data.

Comments

More Reviews of Riak

  1. Home
  2. NoSQL Databases
  3. Riak Reviews
  4. User Review of Riak