Apache Drill vs. InterSystems IRIS

if you're doing joins from hBASE, hdfs, cassandra and redis, then this works. Using it as a be all end all does not suit it. This is not your straight forward magic software that works for all scenarios. One needs to determine the use case to see if Apache Drill fits the needs. 3/4 of the time, usually it does.

Incentivized

Intersystems IRIS is a really great tool for Interoperability. It has so many capabilities out of the box and then such a great developer community on top of that, that there are really no limits to what you can do in terms of data manipulation and translation. Personally I find it to be a great tool if you are looking for Interoperability software.

Incentivized

• queries multiple data sources with ease.
• supports sql, so non technical users who know sql, can run query sets
• 3rd party tools, like tableau, zoom data and looker were able to connect with no issues

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.

• deployment. Not as easy
• configuration isn't as straight forward, especially with the documentation
• Garbage collection could be improved upon

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

if Presto comes up with more support (ie hbase, s3), then its strongly possible that we'll move from apache drill to prestoDB. However, Apache drill needs more configuration ease, especially when it comes to garbage collection tuning. If apache drill could support also sparkSQL and Flume, then it does change drill into being something more valuable than prestoDB

Incentivized

It could do with some additional support for languages and frameworks that are widely used by developers today. For example, it could also integrate the use of AI Coding agents or AI tools to speed up application development processes. It could also include better SSH support to allow developers to remotely edit and maintain applications.

The support team is the best in the world. All you need they can help you. The documentation is very good, but the support team can help you in less than 24h (some hours if it's very urgent).

Also, there is a great developers team in a good community that can help you in several languages (English, Spanish, Japanese, Portuguese, etc.).

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

compared to presto, has more support than prestodb. Impala has limitations to what drill can support apache phoenix only supports for hbase. no support for cassandra. Apache drill was chosen, because of the multiple data stores that it supports htat the other 3 do not support. Presto does not support hbase as of yet. Impala does not support query to cassandra

Incentivized

We are using InterSystems IRIS [especially] for database operations as the query performance is really good for [a large] amount of customer data. You can easily integrate for any application like web, desktop, and many more. It also provides BI functionality which is also very easy to implement using InterSystems IRIS[.]

• Configuration has taken some serious time out.
• Garbage collection tuning. is a constant hassle. time and effort applied to it, vs dedicating resources elsewhere.
• w/ sql support, reduces the need of devs to generate the resultset for analysts, when they can run queries themselves (if they know sql).

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.