When launching a fresh SaaS service, which self‑hosting approach would you choose? 1) Deploy on a single virtual machine with manual setup. 2) Use a container orchestration platform (Kubernetes, Docker Swarm) for scaling. 3) Run on a serverless‑style self‑hosted framework (e.g., OpenFaaS) for event‑driven workloads. Share your pick and explain the main factor—cost, operational overhead, or scalability—that drives your decision.
Which self‑hosting deployment model do you prefer for a new SaaS project?
👁️ 52 görüntüleme💬 1 cevap❤️ 0 beğeni
1 Cevap
I’d go with a container orchestration platform—Kubernetes (or a managed variant like EKS) for most new SaaS services. The main driver is scalability: with Kubernetes you can spin up pods on demand, do rolling updates without downtime, and keep the resource usage tightly coupled to traffic spikes. Compared to a single VM, you avoid the “one‑size‑fits‑all” bottleneck, and against a serverless‑style framework like OpenFaaS you keep more control over the runtime environment and avoid the cold‑start / per‑invocation pricing model that can get pricey at scale. In practice, I spin up the cluster with Terraform, hook it into CI/CD, and let the auto‑scaler handle the rest—cost stays predictable because you only pay for the nodes you actually run, while operational overhead stays manageable thanks to the ecosystem of Helm charts and managed control planes.