HarborCart packages its stateless catalog API as an HTTP container. Demand varies sharply, and its small team wants managed scaling without Kubernetes-specific controls. Which runtime is the best initial fit?

Published
  1. A self-managed Kubernetes control plane on Compute Engine.
  2. Cloud Run with tested scaling bounds and dependency capacity.
  3. A continuously running analytics cluster for the HTTP frontend.
  4. One fixed peak-sized VM with manual release scripts.

Comments — 0