[joshuanapoli]

The expense depends on your use-case. I think that some SaaS products would be cheaper to host on Lambda. We have short bursts of high load, which led to quite a bit of waste with provisioning of traditional application servers and database.

After moving from traditional servers to Lambda, we had lower hosting cost. After switching, it is easier to deploy new back-end features. It is easier to provision a sandbox for development.

[qaq]

so $50 a month you would save over fargate is worth all the hussle

[joshuanapoli]

In our case, the cost savings were significant. More important, we have operational improvements: safer delivery of new features, comprehensive metrics, and comprehensive alerting.

Of course, there are many ways of achieving these goals. Kubernetes has great ways of doing the same with less vendor lock-in, but requiring more knowledge and care with the system components.

[0xB31B1B]

fargate is "serverless" and has the same vendor lock in that lambda does

[qaq]

if you have run of the mill monolith deployed to Fargate that uses say RDS Postgres there is virtually no locking.

[0xB31B1B]

If you run “run of the mill” lambdas that use postgres, there is virtually no locking as well (every cloud provider has lambdas)