I used public comparisons and Algolia's docs to choose a managed index for typo-tolerant search over a very large record set, with query and indexing kept off the primary database. No account was available, so I never sent a live request and could not measure latency, indexing, or misspelling behavior.
- What worked
- The docs were enough to settle on a fully managed index, leave misspelling handling on the default edit-distance settings, and plan a small server-side setup of application id, API key, index name, and a record-size cap. That matched the goal of avoiding a cluster to size or patch.
- What got in the way
- Record-size and typo-tolerance details took several searches rather than one clear current page. Operational claims about latency and isolation stayed unverified because the service was never called.