Absurd nonsense.
Bare Metal compared to GCP or AWS will save you about 75% of your operating costs.
Bare Metal compared to Heroku or Firebase will save you around 90% of your operating costs (a large part of this being caused by bandwidth, which is massively overpriced at Google and Amazon).
With those savings you can usually serve 5 to 10 times as many customers.
That might not be worth it if you’re in SV, and pay your devs the same wages Amazon or Google do (as then you’ll just pay more than with AWS or GCP), but if you’re in places where you pay half the wages Amazon or Google do4 , you can actually save a lot with this arrangement.
I still agree with you, because no one should take setting up and running kube lightly – it’s actually a lot of work.
On the other hand, Google will run your Kube for free up to 5 nodes.
And there’s a few guides for setting it up automatically in vagrant, or on aws, or on Juju-managed clouds.
Sadly, Kube is very barebones – only doing scheduling, if you add a storage provider such as portworx (only block storage) or rook (block and object storage) you also gain that, but it doesn’t do any user auth functionality.
That’s something I’m atm still searching for, something allowing me to easily register and remove users, add them to groups and do RBAC, but without using ldap as backend, and with a way to get it working with OpenID Connect and OAuth 2.0, as well as with Shibboleth, Kerberos, and an LDAP compatibility layer (but with app-specific passwords there).
Fwiw I started on DO and migrated off to get better stability and block storage / proper load balancing. Which DO has since added.
The egress costs for AWS, GCE, and Azure are usually the big cost driver.
So saving on server cost literally did nothing. Our employee cost where 20x, 100x our hardware costs.
Not all startups aim for millions of free uses you will make money off of later.
(The show Silicon Valley actually showed that part quite well)
If we optimized and saved $100 per month on hardware at the cost of even 1 engineer hour, it would be a net loss.
I think a LOT of startups are very simple from the hardware level. You can go real far on just a few servers. And at that level, who care who manages them? Do what is easier.
But why would you buy a VM with this configuration? 32gb of RAM for two boxes, with two i7s that have 4 3.40ghz cores? Lots of people have the impression that cloud is more expensive than owning your own iron, and it probably is, but the difference is made a lot larger if you don't consider TCO and you make no effort to actually adapt your needs to the cloud. Cloud's economics are based around horizontal scaling and provisioning on-demand. If you're hosting in the cloud, you don't get two big machines like this, you shard your app over a bunch of cheap machines and you spin up more/bigger instances to meet peak demand. If you're buying cloud hosting but you go into it with "have everything we need to meet peak load running 24/7," of course it's going to cost you an arm and a leg.
Frontendserver also: Only needs CPU and RAM.