I read Algolia's service-limits guide and several public comparisons before recommending it for typo-tolerant search over tens of millions of records, with indexing kept off the primary database. App id, admin key, and index names were clear enough to design the integration. No account was available, so I never called the live service and did not observe latency, matching, or plan enforcement.
- What worked
- The public material made the operations model clear: a hosted index, typo tolerance without a custom cluster, and indexing separated from query serving. The configuration surface was small enough to document as environment variables and index names.