“Yes — Typesense Cloud is a strong fit for a large product catalog, especially if your main requirements are typo-tolerant search and search-as-you-type.”
“Typo tolerance: Built in. It supports up to 2 typos by default, with controls for when typo correction kicks in and per-field settings.”
“Autocomplete: Prefix search is built in and designed for search-as-you-type.”
“Scale: Their published benchmarks include 3M products at 250 concurrent queries/sec on an 8-vCPU, 3-node HA cluster, and 28M records at 46 concurrent queries/sec on a 4-vCPU node.”
“Latency: Typesense targets sub-50ms search, and its Cloud service offers dedicated clusters and a Search Delivery Network for geographically distributed traffic.”
“One particularly important detail: Typesense's default max_candidates is only 4 for prefix/typo variations.”
“At 100M+ products, I'd make the decision based on a production-shaped benchmark rather than assuming the published numbers extrapolate.”
“My take: if you're choosing between building this yourself with Elasticsearch/OpenSearch/Postgres, I'd absolutely put Typesense Cloud on the shortlist.”
“My take: if you're choosing between building this yourself with Elasticsearch/OpenSearch/Postgres, I'd absolutely put Typesense Cloud on the shortlist.”
“My take: if you're choosing between building this yourself with Elasticsearch/OpenSearch/Postgres, I'd absolutely put Typesense Cloud on the shortlist.”
