Azure AI Search vs. IBM Watson Content Analytics

If you have a medium amount of data (2GB - 2.4TB), high-security concerns, and search is a key requirement in your single-tenant application then Azure Search likely has you covered. If you have a small amount of data per tenant (EG, about 2GB), have low-security concerns, and a multi-tenant application where search is a key requirement, then Azure Search would likely be a good choice - though you would need to implement your own concept of sharding and managing across potentially multiple Azure Search instances. If you can reflect your would-be indexes in Azure Search by depositing the data in columns in a SQL table and just index it for full-text search - and that still fits your requirements - it's probably better to start with SQL Database then scale up to Azure Search when you need the advanced features like ranking or cognitive abilities.

Incentivized

It is well suited for those who are beginners and want to get hands-on with data analysis. It is also easy to learn as the UI is simple and understandable. It can be improved on provided some discounts in the pricing.

Incentivized

• Incredibly robust back-end infrastructure.
• Streamlined integration into Microsoft's Azure Cloud.
• From a user standpoint, it lets the customer easily access their data and provide useful search tips.

Incentivized

• Easy Interface - Drag and click based UI.
• Good amount of tools for visualization.
• Less amount of time taken to perform analysis.

Incentivized

• Like virtually all Azure services, it has first-class treatment for .Net as the developer platform of choice, but largely ignores other options. While there is a first-party Python SDK, there are only community packages for other languages like Ruby and Node. Might be a game of roulette for those to be kept up-to-date. This might make it a non-starter for some teams that don't want to do the work to integrate with the REST API directly.
• In my opinion, partitions inside of Azure Search don't count as data segregation for customers in a multi-tenant app, so any application where you have many customers with high-security concerns, Azure Search is probably a non-starter.
• To elaborate on the multi-tenant issue: Azure Search's approach to pricing is pretty steep. While there is a free tier for small applications (50MB of content or less) the first paid tier is about 14x more expensive than the first SQL Database tier that supports full-text search. For many applications, it makes a lot more economic sense to just run some LIKE or CONTAINS queries on columns in a table rather than going with Azure Search.

Incentivized

• The software is semi-limited to indexing and searching.
• Software does not force a specific "structure" as some document management systems do.

Incentivized

Azure Search is a competitor against Google's own AI autosuggest a feature. We went with Azure because our network security folks found it to be more robust from a security standpoint, which is incredibly important when you have proprietary manufacturing information. Additionally, we're a Microsoft shop so it plugged into our cloud hosting package and client facing OS.

Incentivized

IBM Watson is not quite in the same category as Worldox or NetDocuments as both are full-fledged document management. However, both vendors provide a similar searching and indexing product. Worldox provides searching and indexing but the Indexer is somewhat prone to issues. IBM Watson does not have the stability/consistency issues. NetDocuments is cloud-hosted document management and its index does not seem to have issues. That being said, there is a large premium as the data is all stored in a cloud container with the management system.

Incentivized

• Service cannot be downgrade or upgrade after creation
• Good tool provide maximum ROI

Incentivized

• Organized, easy to produce search results.
• Never lose a document again.

Incentivized