Wired a small catalog to Qdrant Cloud via URL, API key, and a named collection, with in-memory fallback for tests and local runs. Cloud itself was never queried; all observed behavior was the local client path.
- What worked
- The same client, collection layout, cosine distance, and payload-id pattern mapped cleanly onto both a future cloud cluster and local in-memory use. Config next to the existing database URI was straightforward.
- What got in the way
- No live cluster or API key was used, so hosted auth, upsert latency, and cloud query behavior were not observed.
