Algolia offers a wide range of capabilities that can benefit any business by addressing their specific requirements. Integrating with this platform is seamless, and their extensive knowledgebase and training resources are highly valuable for both developers and UI users. We have already witnessed the advantages of this product and are eagerly anticipating future enhancements as we continue to expand our platform, with Algolia as our primary tool for enhancing our search experience.
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.
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.
Recent pricing model changes made Algolia considerably more expensive. I understand that companies change their models all the time, but my plan almost doubled in price overnight. They let me keep my legacy plan for as long as I wanted, but I had already outgrown it, so a small increase in demand caused big price spikes. It's still cheap for what it is though.
The documentation is generally good, but sometimes hard to navigate. I was trying to find examples of how to combine geo-queries with normal ones, and I couldn't find an example, but it wasn't actually hard to figure out.
Some of the advanced features can be hard to understand at first. This isn't really a con, as it just means Algolia is loaded with features, but I was a bit overwhelmed the first time I tried to customize an index.
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.
Algolia is a great tool, we didn't have to build a custom search platform (using Elasticsearch for example) for a while. It has great flexibility and the set of libraries and SDKs make using it really easy. However, there are two major blockers for our future: - Their pricing it's still a bit hard to predict (when you are used to other kind of metrics for usage) so I really recommend to take a look at it first. - Integrating it within a CI/CD pipeline is difficult to replicate staging/development environments based on Production.
Algolia has a good interface and they have done some improvements. However, some non technical users have a challenging time in the use for the first days of learning. But once the main aspects are learned is a straight forward operation
Performance is always a major concern when integrating services with our client's websites. Our tests and real-world experience show that Algolia is highly performant. We have more extremely satisfied with the speed of both the search service APIs and the backend administrative and analytic interface.
It’s non existent. No tech support and no customer service… my application was blocked and is currently inactive causing huge business disruption, and I’m still waiting days later for a response to an issue which could be resolved very very quickly if only they would respond. Very poor from a company of that size
While AWS's offering is a typically cheaper solution, it requires a lot of work to gain any of the core features of Algolia. The cost of dev time and long-term maintenance would be more than the costs incurred with Algolia, which is why it made the most sense financially. On the engineering side, we could give our stakeholders access to Algolia to adjust the indices themselves, which would allow us to focus on other work.
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.
Overall is a scalable tool as the environment and the backend functions are the same and many things are done directly on the tool so without the need of further specific developments. However some things could be improved such as documentation for integration that could help in doing whitelabel solutions
Users who had abandoned our product (attributing slow search speeds as the reason) returned to us thanks to Algolia
We used Algolia as our product's backbone to relaunch it, making it the center of all search on our platform which paid off massively.
Considering we relaunched our product, with Aloglia functioning as its engine, we got a lot of press coverage for our highly improved search speeds.
One negative would be how important it is to read the fine print when it comes to the technical documentation. As pricing is done on the basis of records and indexes, it is not made apparent that there is a size limit for your records or how quickly these numbers can increase for any particular use case. Be very wary of these as they can quite easily exceed your allotted budget for the product.
