Enterprise-tier example: typo-tolerant instant search over a product/document catalog — Algolia or Elasticsearch instead of a dedicated Lucene engineer
Created 2026-06-21
Summary
Claim: Search over a product / document catalog — Algolia founded 2012 (Dessaigne & Lemoine; Y Combinator W2014) — search-as-a-service, no infra to manage or Elasticsearch first release 2010 — open-source on Apache Lucene; commodity search deliver typo-tolerant instant search that previously demanded a dedicated Lucene/Solr engineer ([[pre-elasticsearch-sql-like-or-custom-lucene]]).
Source: Synthesis of the search entries.
Confidence: Industry-consensus.
Why this matters for Candid: Third canonical worked example. The "search across our products / our docs" feature is the cleanest single capability that went from person-month-build to configuration-choice.
Related entries
Depends on
Related
- reference Pre-Elasticsearch site search: weak SQL LIKE queries or a costly custom Lucene/Solr build
- rule R3 — Rent the commodity parts (Stripe / Auth0 / Algolia / RDS / Lambda); build only what is genuinely differentiated logic
- reference Research brief: the searchable, structured catalogue as a working tool — when records-not-prose pays off (June 2026)