Azure AI Search (formerly Azure Cognitive Search) is enterprise search as a service, from Microsoft.
$0.10
Per Hour
IBM Watson Discovery
Score 9.0 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.
IBM Watson Discovery resulted more robust and performant, also the insights were much more interesting than just an AI search from Microsoft or a prompt for ChatGPT.
Discovery differs from its competitors due to the better ease of implementation and the high level of natural language recognition, it is equal in integration resources such as API and workflow or process pipeline, but it loses in the price for a high volume of documents and/or …
Incredibly robust software for an enterprise organization to plug into their application. If you have a full development resource team at your disposal, this is great software and I highly recommend it. Largely, however, you won't be able to use this prior to the enterprise level. It's just too complicated and cumbersome of a product.
Overall, IBM Watson Discovery is an amazing technology that we use with our clients to address various business problems, but the biggest challenge has always been about ingesting, analyzing, enriching, and searching huge collections of documents and allowing our end users and SMEs to be able to search for what they need to reduce the time and efforts spent daily on a manual search through various collections of documents. We have successfully managed to reduce manual work by over 80%, and now our SMEs are being used for the skills they have to gather insights rather than do manual work.
Azure Search provides a fully-managed service for loading, indexing, and querying content.
Azure Search has an easy C# SDK that allows you to implement loading and retrieving data from the service very easy. Any developer with some Microsoft experience should feel immediate familiarity.
Azure Search has a robust set of abilities around slicing and presenting the data during a search, such as narrowing by geospatial data and providing an auto-complete capabilities via "Suggesters".
Azure Search has one-of-a-kind "Cognitive Search" capabilities that enable running AI algorithms over data to enrich it before it is stored into the service. For example, one could automatically do a sentiment analysis when ingesting the data and store that as one of the searchable fields on the content.
It's an enterprise level product so you need to have the budget for it.
Challenging-to-impossible for a non-technical administrator to implement.
It further locks you into Microsoft's ecosystem and doesn't play well with non-Microsoft software. Depending on your point of view, this can be a pro or a con.
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.
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.
As I've mentioned, the biggest competitor to Azure Search is actually Azure SQL Database. It doesn't have as many features, but it's more economical and most .Net applications will have one already. As long as you can arrive at a schema and ranking strategy, it's a "good enough" solution. There are a variety of search technologies (Lucene, Solr, Elasticsearch) that implement a search service. Some of them are even open source, though I would only say "free" if you do not value your time. They most likely need to be hosted via Container (or VM if you're old school), so you're incurring DevOps costs to not only set them up but monitor and maintain them yourself.
If you're already on AWS, there is almost no reason to use Azure Search. Unless you're already multi-cloud, desperately need the cognitive abilities, and don't mind a potential performance hit from looking across datacenters (hey, it could happen), you should probably just use Amazon CloudSearch.
Discovery differs from its competitors due to the better ease of implementation and the high level of natural language recognition, it is equal in integration resources such as API and workflow or process pipeline, but it loses in the price for a high volume of documents and/or research. If you own or plan to use other services from the IBM Watson family, there is no doubt that Watson discovery is your best option. Another important point is if you plan to use a cloud or on-premise service (local server or private cloud).
