Elasticsearch is an enterprise search tool from Elastic in Mountain View, California.
$16
per month
IBM Watson Discovery
Score 8.8 out of 10
N/A
IBM offers Watson Discovery, a natural language processing (NLP) application with options to measure sentiment, detect entities, semantic roles, and other concepts.
Elasticsearch is really well suited for searching text (Natural Language Processing) and you can fine tune the searches and scoring very well. I like the ability to find Significant Terms in the Index, where you can find aggregations that are really relevant to a specific search. It also allows for queries to lead to new queries via aggregations which is great for navigating your data. It is less suited to doing more complex aggregations where slices of data are required to be processing using guassian normalizations. And doing searches which join different documents is very very hard, and requires serious thought on how to denormalize data.
Whether using it as a standalone search tool, integrating with other IBM Watson products, or using the API to integrate with proprietary or third-party systems and applications, Watson Discovery addresses these and many other scenarios where document search is required -- understand- if here documents can be pdf, doc, txt files, websites, among other formats --, don't confuse Watson Discovery with EDRMS (Electronic document and records management system) software, Discovery goes further, allowing text search to be done within a context using natural language (NLU) and returning not only the search term but also insights and related issues. File indexing works very well, and training Discovery so that documents and technical terms are learned a bit of work, but it can be reduced by using some of the learning models already trained and available for use.
Setting Java memory thresholds can be a pain for those not accustomed to things like Eden Space & Old Generation which can lead to over allocation, or more likely, under allocation. Apache Solr had a similar issue. It would be nice if the program would take an extra step and dogfood it's own advice by analyzing the system & processes to return a solid recommendation for that configuration. The proper configuration information is outlined in the documentation, it would be nice if that was automated.
The only health check that ElasticSearch reports back is a "red" status without any real solid information about what is going on, though its usually memory thresholds or disk I/O. I am currently on ElasticSearch 1.5 so that may have changed for newer versions. When the status goes "red", I as the administrator of the software, feel like I lose control of whats going on which should rarely happen. Something more verbose would eliminate that.
This is more of a critique of the ElasticStack in general. The whole top to bottom stack is starting to get feature creep with things that are better suited in other software and increasing the barrier for entry for people to get started with setting up a robust logging infrastructure. ElasticSearch as a storage search engine, is pretty streamlined, but I can see that the tools that comprise the ELK Stack are going to require a certification with constant study at some point. During major release for Logstash a while back, it literally took a month to learn a new language because Elastic completely changed the syntax. For a medium sized organization of only a couple of admins, that is a pretty high bar where time is money. They really should work on refining/automating the tools & search engine they have, instead of shoehorning/changing things on to an already rock solid foundation.
I believe AI should be more flexible about providing data. However, it's understandable that you need to provide the details you need in a more specific and detailed way.
The interface could use more tweaking. Being new to the program, it was kind of hard to navigate.
Luckily, there was a customized feature of the dashboard that I could set up, and having something that you know where you are placed always feels familiar and comfortable.
To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
IBM Watson Discovery has the best user capabilities and easily transform business decision-making portfolio. The automation system saves time used in data analysis as opposed to manual research that consumes a lot of time. The visualization across the dashboard enables my team to interpret complex data and use it to make reliable marketing decisions.
We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
Similar to all IBM Watson and Salesforce product solutions, the overall support would be a 10/10. Their provided FAQ's help with frequently experienced issues and if still unable to figure something out, their customer service representatives are always super responsive. With instant chat functions available, it is easy to ask a quick question rather than sitting on hold.
Elasticsearch is the most well-known and supported free data platform that we identified. We are taking advantage of community knowledge and practices. In terms of flexibility and breadth of use cases no other competitor came close to Elasticsearch. We've tried Solr in the past be we encountered issues which were deal-breaking for us. MongoDB - it just did not pass our evaluation parameters as a main data platform. We still use it for smaller purposes, though.
To be entirely honest, in my review, I have used Elasticsearch in the past, but not in a way similar to that I am using Discovery, and I cannot honestly say that I can compare the two because I used Elasticsearch in infrastructure management and monitoring setup while using the ELK stack (Elasticsearch - Logstash and Kibana).
I am not in finance and I suspect even if I was this would be hard to measure. But for sure, Elasticsearch has enabled us to have the most flexible data model in the industry for our customer's data, and in doing so we have attracted many many technical customers and got much of their $$$.
One problem with Elasticsearch is that because it runs on the JVM, there can be some stop-the-world JVM garbage collections happening that can take down nodes and reduce indexing speed. The solution for that tends to be "let's just upgrade the CPU on that machine". And before you know it you are paying $$$ because this'll happen with 40+ machines.
On the other hand, I do think that ES is more efficient than other systems and so it requires fewer nodes to keep it highly tolerant and available, so we probably saved some money that way.
IBM Watson Discovery has had only positive impacts on our overall business objective of providing quality customer service and timely resolutions for our clients.
The use of this integration has made life easier for our customer service team, who can now resolve cases for customers quicker and easier.
Our company prides itself on the service and expertise we're able to provide for our customers and IBM Watson Discovery has only made that task easier for our employees to perform.
