Apache Drill vs. Progress MarkLogic

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

In an area where it will be built once and maintained, it shines. If you aim to use CI, temporary environments, or anything else, it is not very effective. Licensing is almost impossible on boxes that are to be created on the fly.

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

• Indexing is a major strength of MarkLogic. The out-of-the-box configuration is set up to handle a combination of text and fielded data. The indexing is also highly configurable. Those configuration options are at the heart of a lot of our high-volume, high-performance applications.
• The industrial strength transactions and security are also a strength, particularly when we are dealing with user-created intellectual property.
• The engineering support is a strength. They are big enough to have a really strong support and engineering staff, but small enough so that a medium-sized customer has access to it. They are very responsive to questions and problem reports.
• The ability to move easily among XML and JSON is a strength.

Incentivized

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

Incentivized

• How to do complete data profiling on documents loaded in Marklogic database?
• Customers need a tools which can be customized to suit their data profiling needs but currently the tools which MarkLogic provides fall short on this requirement.
• Unit testing framework which is using only XQuery as the language is lacking some features.

Incentivized

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

Our firm has consultants for a number of technologies/disciplines. While I am capable and experienced in other areas, my preference is always to work on engagements with MarkLogic. As an architect and developer, I get far more flexibility and performance from one product instead of cobbling together a stack of several products to provide a capability that MarkLogic has rolled into one great product.

Incentivized

Very little about it can be done better or with greater ease. Even things that seem difficult aren't really that bad. There's multiple ways to accomplish any admin task. MarkLogic requires a fraction of administrative effort that you see with enterprise RDBMS like Oracle. MarkLogic is continually improving the tools to simplify cluster configuration and maintenance.

Incentivized

There's always room for improvement. Some problems get solved faster than others, of course. MarkLogic's direct support is very responsive and professional. If they can't help immediately, they always have good feedback and are eager to receive information and details to work to replicate the problem. They are quick to escalate major support issues and production show-stopping problems. In addition to MarkLogic's direct support, there are several employees who are very active among the community and many questions and common issues get quick attention from helpful responses to email and StackOverflow questions.

Incentivized

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

In comparison to both Mongo and HBase, MarkLogic wins in terms of integration to other systems, while loosing in terms of pricing. In terms of documentation all will be in same range putting MarkLogic a bit forward.

Incentivized

• 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

• It took longer than expected to develop our application and get the level of consistent performance necessary. As a result, profit was flat for a couple of years but the benefits are really starting to kick in.

Incentivized