InterSystems IRIS vs. Riak

It is best suited in the scenario where a single interface is required for providing [a complete end-to-end] solution to the customers. You don't need [a] separate platform to write code or [perform] database operations. All you need is InterSystems IRIS software and you are done. You can also use analytics functionality which is one of the greatest [features] which many customers need for their solution[.]

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

• Connecting with mutliple vendor platforms and systems allowing us to consume and provide data as needed.
• Allowed us to implement our own RESTful api engine to server data to our internal applications.
• Setting up their recommendations for high availability allow us to perform server maintenance with minimal down time to our users.

• 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

• Enhanced documentation, more comprehensive and user-friendly documentation, including detailed tutorials and examples
• Improving compatibility and integrations with others programming languages
• Introducing tools and techniques to optimize the performance of ObjectScript applications, such as profiling tools, performance monitoring utilities, and code optimization guidelines
• A better compatibility with Python libraries

• 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

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

The interface is very intuitive, the documentation is very good so it is not complicated to operate.

The security is complex, but you can create a special role to access and the user ONLY can operate with the part that it allows.

Also, you can examine the data very quick with the SQL Browser integrated.

The InterSystems WRC has always been helpful and responsive. The folks I have spoken with are always understanding of our needs and questions and regardless of if the question is simple or complex we are always met with the same professionalism and helpfulness every time. I have no hesitations contacting InterSystems for help!

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.

Will done based on a proper planning, so this will makes execution more easier and better.

Tibco was not originally planned to be used for HL7 Integrations and as such we had to create some very complicated processes in order for the messages to parse and validate appropriately. It was simply not built for this type of interoperability. Comparatively, InterSystems IRIS for Health (HealthConnect) has out of the box HL7 features that would parse messages, offer a variety of validation options, simplified data lookups and transformation and reduced the amount of time it took to develop connections with out vendor systems. InterSystems IRIS also allows one to push just single files into production at a time so there is less of a chance of us pushing something that should not be in production yet as our previous system was set up to with TIBCO deployments

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.

• Very Fast and scalable software to deal with big data flow, safe and robust.
• The studio IDE is quite old fashion and lacks a few facilities
• amazing for complex data consumption, its milyi-model capability wich allows multiple different models for a single set of codes.

• 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