3 ms·

100% agreed. But I'd suggest you just go for a serverless offering from one of the big cloud players. If your app runs on Heroku or Fly.io, you really don't ne

100% agreed. But I'd suggest you just go for a serverless offering from one of the big cloud players. If your app runs on Heroku or Fly.io, you really don't need servers or VPCs or k8s clusters. Where I work, we've gone all-in on AWS Serverless and couldn't be happier. We have 1 dev-ops/infra person supporting 3 feature teams, all of which are releasing into their apps based on this stack multiple times a day. The infrastructure overhead is so low that our dev-ops guy has time to additionally spend time on optimising CI/CD for speed, tightening up on security, etc, etc. When we started, we had 2 devs who just did everything from a single repo, a gitlab account, and the serverless framework. I really don't understand how adding yet another layer on top of AWS's / GCP's / Azure is materially going to change the developer or user experience. It just adds cost.

ignoramous 4y ago
> I really don't understand how adding yet another layer on top of AWS's / GCP's / Azure is materially going to change the developer or user experience. It just adds cost. Actually, AWS products (PaaS like Lambda) themselves are a layer atop AWS (IaaS like EC2) that you just said you immensely favour, and that it reduced costs (1 devops for 3 teams). Besides, Snowflake and Databricks are two examples among many of non-AWS but AWS-dependent billion dollar software shops that work just fine for the largest of enterprise businesses. That said, don't think Fly is a layer on top of AWS (they rely on servers from NetActuate, Equinix, and others from the looks of it: https://news.ycombinator.com/item?id=29162706 https://news.ycombinator.com/item?id=29162706). They couldn't have the pricing they do if they were.