Apache Solr vs. IBM Watson Explorer

Very effective for end-user searching applications and for generating search results. Also very well suited to those looking for high reliability and performance. If [you're doing] fuzzy searching or if you are working on a smaller end-user application or an internal application that does not require high performance and flexible/adapting searching then it may not be necessary to use Solr.

Incentivized

The Watson Explorer is great because it potentially replaces a meriad of other low-level analytics products that we would need to use for data analytics and data mining. WEX isn't really suitable much beyond doing text and data analytics and performing machine learning, so if your team doesn't really have a use-case that fits all of these categories, it is worth looking at an alternative.

Incentivized

• Faceted navigation and field collapsing/grouping : filtering and quick results were what we needed for our websites. Our customers needed to have this functionalities for good and efficient results.
• We tested them with our customers' registered searches (they received all new goods matching with their registered searches by emails and/or mobile push). Results were incredible by comparison with our old system (old MySQL requests).
• Note : we didn't put all our data in Solr. Just what we need for searching uses. Other data stayed in our MySQL database.
• Auto-suggest : our old auto-suggest wasn't performing well. With Apache Solr, our new one was worked really well ! The suggestions came quickly and suggestions were good.
• We also extended auto-suggestion with geo-spatial data and it worked well.
• Hit highlighting : we used this functionality and we didn't have problem and nasty surprise.
• Keep all data status during data upgrading (see next details for improvements)

• Free to try - It's possible to use most of the useful features of Watson Explore on their trial/demo accounts.
• Super well-designed data analytics tool - Most of the tools and features of the explorer are really useful, and truly help you fully understand the depth of any format of textual data.
• Extensive sources compatibility - WEX can retrieve data from a large range of sources, and the compatibility there is quite good as well.

Incentivized

• Ease of use -- this is not always the easier platform to configure.
• Developer Community -- There are not a whole lot of folks out there that understand this stuff so finding talent is difficult.
• Drupal 8 -- We've been frustrated with slow development on APIs for Drupal 8 integration.

Incentivized

• Support is just OK, like most of the other IBM Watson products. The setup/integration is really hands-on, but it's also problematic because support later may take a considerable amount of time.
• UI could still use a little more improvement - part of the administration and sources dashboards are hard to navigate.
• The Application Builder is a great part of the product, but hard to learn/understand - this is where we needed the most support from IBM and tutorials/documentation.

Incentivized

It takes some time to deploy and currectly maintein it. And also, to learn how to use and integrate in the enviroment as well. Once you get theses steps done, it usability is very simple, and almost of the time it don't require no further attention on it. Even for maintence, if you deploy it on a cluster mode, it is very reliable and easy to take one host down.

Incentivized

We switched from search indexes stored in MySQL to soar and it's made a world of difference for our growing businesses. The relational databases are very poor for handling the complex data searches require and Solr delivered all the tools we need to get the performance our end users are demanding.

Incentivized

Google Cloud offers a Natural Language product, but it is just an API. This API doesn't offer the useful visualizations of relations, analytics, and graphs that IBM Watson Explorer offers on their interface. For this reason, we chose to go with IBM WEX. For later stages of our production, we decided to use Google's NLP API because we found that it was quick to integrate into production after studying data and developing models using IBM WEX.

Incentivized

• It's enabled us to deliver fast, relevant search results on our new website. The site is still in beta and being actively developed so our complete ROI is still unknown.
• It integrates very well with Drupal so it has saved us from having to develop a custom solution.

Incentivized

• Positive - Trial/demo period. This was really useful for us to figure out what features of WEX we liked most and how difficult it would be to integrate WEX into our workflow.
• Negative - On-boarding was long and almost always requires support from IBM support, unlike most other products this advanced.
• Positive - WEX replaced a large selection of alternative products we would have to use for the same functionality, and having all of that function in one place was definitely helpful.

Incentivized