3 posts tagged with "Comparison"

"Should we use Solr or Elasticsearch?" is one of the most common engineering questions when a search project starts. It's also slightly the wrong question. Solr and Elasticsearch are search engines: they index and rank documents. What most teams actually need is an enterprise search platform: connectors, facets, multi-language, semantic search, RAG, and an admin UI on top of that engine.

That's the distinction this post draws, and where Viglet Turing ES fits, because it's not a competitor to Solr/Elasticsearch. It runs on them.

If you run a large content portal (intranet, knowledge base, support site, or a public site on Adobe AEM), you have probably evaluated Coveo and Lucidworks Fusion. Both are mature, capable enterprise search platforms. This post compares them head-to-head with the open-source option, Viglet Turing ES, so you can see where each fits.

We covered the open-source alternatives to Algolia and Coveo for AEM broadly; this one zooms into the enterprise-portal end of the market.

If you run Adobe Experience Manager and need a real search experience, with facets, autocomplete, relevance, and increasingly AI answers, you'll quickly hit the limits of out-of-the-box Oak indexing and start evaluating a dedicated search layer. The usual shortlist is Algolia, Coveo, and Lucidworks: all excellent, all SaaS, all priced per document and per query.

This post lays out the trade-offs honestly, including where the open-source option, Viglet Turing ES, fits and where it doesn't.