Apache Geode vs. InterSystems IRIS

The biggest advantage of using Apache Geode is DB like consistency. So for applications whose data needs to be in-memory, accessible at low latencies and most importantly writes have to be consistent, should use Apache Geode. For our application quite some amount of data is static which we store in MySQL as it can be easily manipulated. But since this data is large R/w from DB becomes expensive. So we started using Redis. Redis does a brilliant job, but with complex data structures and no query like capability, we have to manage it via code. We are experimenting with Apache Geode and it looks promising as now we can query on complex data-structures and get the required data quickly and also updates consistent.

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

• Super Fast data pull/push
• Provided ACID transactions, so it works like a SQL Database
• Provides replication & partitioning, so our data is never lost and extraction is super fast. NoSql like properties

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.

• Needs more supporting languages. Out of box Python, Nodejs adapters would be wonderful
• Currently it supports just KV Store. But if we could cache documents or timeseries data would be great
• Needs more community support, documentation.

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

Still Experimenting. Initial results are good. we need to figure out if we can completely replace Redis. Cost wise if it makes sense to keep both or replacement is feasible.

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.

Never contacted support

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.

Still Experimenting. But looks promising as it has query capabilities over complex data structures

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

• Still experimenting so difficult to quote
• For a small size project/teams might be an overkill as it still has certain learning curve
• For Medium to large projects with complex Data Structures that need to be queried with a fast o/p it definitely works

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.