Chose the hosted search service as the low-operations way to serve misspellings without indexing on the primary database. App setup is an application id, an API key, and an index name per environment. The Rails-oriented notes covered searchable attributes, but queued updates, safe deletes, and settings serialization still had to be traced in library code. No credentials were available, so the live service was never called.
- What worked
- The documented model matches the need: typo tolerance by default, a separate index, and no cluster to run. Configuration is a key pair plus an index rather than operating a search cluster.
- What got in the way
- There was no account to exercise the real API, so latency, typo behavior, and indexing were not observed. Integration notes left queueing and settings mapping incomplete enough that the client implementation had to be read directly.