Azure Cosmos DB vs. Riak

NoSQL platforms are very useful when it comes to security, speed, accuracy, high accessibility with high read and write power. Everything is managed under the cloud and we have the various capabilities of Azure and support for Microsoft products with us. Flexibility in price and variety of features, as well as real-time results, are some of the popular [features] of this platform.

Incentivized

Riak is very good if you need a resilient data store that can handle large amounts of documents very fast. If you have 1,000,000 documents and need to execute complex queries, it is great. Riak's SOLR engine is fast, however if you have extremely high amount of queries in a very limited time range, it can fail in a bad way.

Incentivized

• Turn-key geo-redundancy with multi-master writes is unprecedented and unparalleled in the industry!
• Guaranteed low latency makes Cosmos DB an excellent fit for most of our performance-intensive situations.
• The tunable consistency model simplifies so many challenges in distributed systems engineering that otherwise require advanced knowledge of computer science topics. I continue to be impressed at how Cosmos DB has abstracted away so much complexity.

Incentivized

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

Incentivized

• When searching by default, it is case sensitive, which must be changed by default
• In many ways, the price should be more flexible according to the requested facilities, because the price is very expensive for startup companies.
• It is not fully compatible with most common Streaming Analytics tools applications and developers should be worked on it

Incentivized

• Missing a free text search function
• More security work
• Multi-tenant reporting
• More types of index optimised for different structures
• Automating repairs especially after unclean shutdowns
• WebDAV/Samba shares for Riak CS
• Implementing the SQL queries from Riak TS in Riak KV
• Settable replication bandwidth caps
• Safemode start up after failure
• More client integrations

It's efficient, easy to scale, and works. We do have to do a bit of administration, but less now than when we started with this a couple of years ago. Microsoft continues to improve its self-management capability.

Incentivized

Riak works great for our use case but the fact that deletes seem to resurrect is a real issue for us. Unless we can get this solved, we'll continue to look at other products to see if our use case fits. Otherwise Riak is a great product and it fits our use case 95%. We have found work arounds to the remaining 5%.

Incentivized

Like I said, Cosmos is the way to go. From all of the services that Azure has, Cosmos is very robust in terms of usability. It's ever-evolving and integrates with other applications seamlessly. The interface is pretty easy to understand. I implemented various solutions for my company and Cosmos was one of them.

Incentivized

The support team is very responsive and we are generally satisfied with Microsoft support, in my opinion support team of a product and service is just as valuable as its quality and performance. Telephone answering, 24-hour hotline, email support and ticketing are excellent.

Incentivized

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.

Azure Cosmos DB for MongoDB is more affordable than many other solutions and works incredibly well if you're within the Azure ecosystem.

Incentivized

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

Amazon S3 is a nice tool but when you are at significant scale with regionally specific data (joys of GDPR), it's much easier to keep it in house and Riak CS lets you do exactly that. All you need to do is point your application at Riak CS instead of Amazon S3 and it just works as if nothing has changed.

When we evaluated against Cassandra, we found the tools available did not match our needs at the time.

• Expensive but works if your infra is on Azure data center.
• No latency and nearly no downtime.
• Takes time for end users to adapt.

Incentivized

• Riak's simple API and simple management model made it a no brainer when it came to adopting it as a technology for the team.

Incentivized