undefined | Better HN

0 pointsp_l5y ago0 comments

Hard disagree.

What k8s really scales is the developer/operator power. Yes, it is complex, but pretty much all of it is necessary complexity. At small enough scale with enough time, you can dig a hole with your fingers - but a proper tool will do wonders to how much digging you can do. And a lot of that complexity is present even when you do everything the "old" way, it's just invisible toil.

And a lot of the calculus changes when 'managed services' stop being cost effective or aren't an option at all, or you just want to be able to migrate elsewhere (that can be at low scale too, because of being price conscious).

0 comments

preommr5y ago

> but a proper tool will do wonders to how much digging you can do.

Then the question becomes "Is K8 more of a shovel or an excavator". I think its fair to say that its more the latter.

gatvol5y ago

We have a mature TF module library and can roll out complex, well configured infra in a matter of hours, reliably. That said it's platform specific.

Sure, managed service costs are certainly a thing, but to my point that only really start to become an issue at significant scale, assuming you're well configured.

p_lOP5y ago

Or when you're small bootstrapped company.

The cost metrics that make "it's cheaper to use managed service than pay the cost of extra engineer to specialize in infrastructure" aren't universal. In fact, I usually have to work from the opposite direction, where hiring a senior Ops specialist who can wrangle everything from shelving the physical hw to network booting k8s cluster on-premises can be cheaper that Heroku/AWS/etc.

j / k navigate · click thread line to collapse