Chose managed Elasticsearch on Google Cloud over a self-managed fork so search could sit beside existing Cloud Run services without adding Kubernetes. Wrote the production plan and app config for URL, API key, private connectivity, and snapshots, but never provisioned or queried a live deployment.
- What worked
- The managed GCP offering mapped cleanly onto an existing Cloud Run, Cloud SQL, and Pub/Sub stack: same-region hosting, secret-mounted credentials, and private connectivity were easy to specify without changing the source-of-truth database.
- What got in the way
- Standing it up still implied extra platform work that is not in the application repo: VPC egress from Cloud Run, Private Service Connect, secret storage, snapshot configuration, and creating the cluster itself. None of that could be verified in this task.