Apache Cassandra vs. InterSystems IRIS

Cassandra excels in a broad range of applications -- especially if you understand its data model and write your applications accordingly. It's an excellent choice for time-series data, and a poor choice for application queues. It performs the best if you can simply record history and compute from it, rather than going back and editing or deleting things a lot.

Incentivized

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[.]

• High Availability - we utilize the data replication features of Cassandra. This enables us to access our data even when several nodes have gone down
• Data Locality - our architecture combines Cassandra storage nodes and computation nodes in the same machine. This enables us to utilize data locality and limit expensive network IO to read data.
• Elasticity - Cassandra is a shared nothing architecture. Nodes can be added very easily and they discover the network topology. As soon as a node has joined the Cassandra ring, the data is redistributed among the existing nodes and streamed to it automatically.

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.

• No Ad-Hoc Queries: Cassandra data storage layer is basically a key-value storage system. This means that you must "model" your data around the queries you want to surface, rather than around the structure of the data itself.
• There are no aggregations queries available in Cassandra.
• Not fit for transactional data.

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

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.

Incentivized

It’s great tool but it can be complicated when it comes administration and maintenance.

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.

Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.

Incentivized

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!

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

Apache Cassandra has the best of both worlds, it is a Java based NoSQL, linearly scalable, best in class
tunable performance across different workloads, fault tolerant, distributed, masterless, time series database. We have used both Apache HBase and MongoDB for some use cases which were within hadoop setup and JSON (JavaScript Object Notation) document store respectively, but given the overall factors favoring Apache Cassandra, it is a technology choice for multiple platforms!

Incentivized

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

• The open source version of Cassandra is only suggested for learning the basic concepts and play with its core features. Unless you really want to invest a lot in your developers and architects knowing every detail of Cassandra, I prefer the DataStax enterprise version. Although the license cost is relatively high, I think they it is worth it. I'm thinking about the support, the monitoring tool OpsCenter, and the integration of Solr and Spark (for data analysis).
• Cassandra didn't fully replace our old and traditional relation database Oracle. In addition, it opens another door for us to deal with some special business use cases that NoSQL database can do better in a more feasible and efficient way.

Incentivized

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