3 ms·

Why did a startup need to manage K8s? Why does using the cloud preclude a monolith? My app is a stateless monolith hosted with Fargate and RDS. I don't have to

Why did a startup need to manage K8s? Why does using the cloud preclude a monolith? My app is a stateless monolith hosted with Fargate and RDS. I don't have to think about K8s, or look at it, or know how it works. The pricing is relatively garbage, but it doesn't matter: now I don't have to think about devops as a concept. I don't get how people are screwing up this cloud thing: it's as simple as you make it. Being pennywise and pound foolish trying to engineer complex solutions on the "cheaper" parts of cloud providers makes absolutely zero sense to me. 9 times out of 10 you hear X startup paying stupidly expensive bills it's because they tried to build out something that the cloud provider would have provided with a 50% markup but with an architecture you can't screw up.

gigatexal 3y ago
> Why did a startup need to manage K8s? Why does using the cloud preclude a monolith? Because we were dumb and thought k8s meant we had to go microservices. > if the app can fit on a single VM … Well of course. If and when it out grows the vm hopefully you’ve found product market fit and are bootstrapped and making money and have hired proper platform and dev teams to do it right and the single VM PoC is redone. Or so that is what we are sold. In reality things happen piece-meal and more chaotically.
thraxil 3y ago
Yeah, we've got the GCP equivalent with a monolith running on Cloud Run, Cloud SQL, Cloud Load Balancer, and a few misc services that are pennies per month (Tasks, Scheduler, Secrets Manager, Cloud Build, etc). Scales elastically, all kinds of niceties around security, backups, observability, zero downtime deployments, preview environments, etc. that required basically no work from us to build. Handles a lot of traffic for cost that's in the range of hundreds per month. Devs spend basically no time on any of that after the initial setup and can focus entirely on development. I could build all of that out on some VMs or hardware (I've done all that stuff in the past, racking servers, managing Xen, DRBD, database clusters, etc) and probably save a little bit of money, but nowhere near enough to justify all the extra time and distraction. If we outgrow Cloud Run, it's an easy path to GKE or if we grow to where the cost is worth staffing out, it could all run on VMs or hardware without significant changes. In the meantime, I'm not worrying about NICs failing, OS packages needing to be patched, and so on.
- gigatexal 3y ago
  Yeah. That’s why I love building on GCP: things just work so nicely together and there’s far fewer foot guns than AWS

gigatexal 3y ago

> Why did a startup need to manage K8s? Why does using the cloud preclude a monolith? Because we were dumb and thought k8s meant we had to go microservices. > if the app can fit on a single VM … Well of course. If and when it out grows the vm hopefully you’ve found product market fit and are bootstrapped and making money and have hired proper platform and dev teams to do it right and the single VM PoC is redone. Or so that is what we are sold. In reality things happen piece-meal and more chaotically.

thraxil 3y ago

Yeah, we've got the GCP equivalent with a monolith running on Cloud Run, Cloud SQL, Cloud Load Balancer, and a few misc services that are pennies per month (Tasks, Scheduler, Secrets Manager, Cloud Build, etc). Scales elastically, all kinds of niceties around security, backups, observability, zero downtime deployments, preview environments, etc. that required basically no work from us to build. Handles a lot of traffic for cost that's in the range of hundreds per month. Devs spend basically no time on any of that after the initial setup and can focus entirely on development. I could build all of that out on some VMs or hardware (I've done all that stuff in the past, racking servers, managing Xen, DRBD, database clusters, etc) and probably save a little bit of money, but nowhere near enough to justify all the extra time and distraction. If we outgrow Cloud Run, it's an easy path to GKE or if we grow to where the cost is worth staffing out, it could all run on VMs or hardware without significant changes. In the meantime, I'm not worrying about NICs failing, OS packages needing to be patched, and so on.

gigatexal 3y ago
Yeah. That’s why I love building on GCP: things just work so nicely together and there’s far fewer foot guns than AWS