[withinboredom]

They probably do make more money… actually. At least in net profit.

Cost in time to setup a bare metal, production quality k8s cluster with all the bells and whistles from the cloud: 2 weeks and a skill I will have forever. In fact, the second cluster took 4 hours.

Monthly cost: $240 per month.

Time to spin up a new worker, using cloud compute for elastic load beyond base load: 5 minutes.

Base load capabilities: 120ish cores, 1tb ram, ridiculous terabytes of storage.

Cost to run on managed k8s in the cloud: $5-20k per month.

[theamk]

We are talking lambdas here, not 1TB ram workers.

I had to run a authenticated webhook forwarder outside of the out firewall. Yes, I could have made a real machine, but I've made a lambda instead. It's costing us less than $2/month and I spend zero energy on maintenance, security checks, etc. And all config is in a single git repo that anyone can read and understand - there is zero chance of someone ssh'ing into server for a quick fix, then forgetting to record what they did.

Real machines are great for heavy loads, but you just cannot beat lambdas for the lightweight stuff.

[diesal11]

> They probably do make more money… actually. At least in net profit.

It's my company so I think I'd know :)

Also what exactly are your estimates here? Where are you getting that kind of capacity for $240 a month?