Most of these are what I'd call "cloud in name only" providers - everyone uses the term but you would have significant challenge moving a cloud workload that makes use of the higher layer abstractions to these.
There are very few workloads that require more than what you can accomplish with a handful of VMs. Using tools like Terraform makes it a lot easier to abstract away the specialised services.
I work with a couple workloads that can’t even be completely deployed in cloud environments. Those aren’t common.
The vast majority of companies can get along with a Google office license and a Wix website.
Not everyone works at a company with hundreds of thousands of employees and hundreds of millions of users.
I agree RDS, Aurora, Big Query, S3, load balancers, declarative security policies, artifact repositories, managed auto-scaling clusters and so on are very convenient, but they aren’t a requirement.
You “worked with a couple of workloads” and that’s what makes you an expert on infrastructure and architecture at scale?
Your LinkedIn profile is your HN profile. I see you have worked at some large well known companies. How can you possibly not have been exposed to some large deployments?
And none of those is “the simple case” I alluded to. The vast majority of businesses need, perhaps, email, file sharing, instant messaging and, perhaps, a website. They won’t train their own ML models, nor have parallel sysplexes of mainframes spread across multiple datacenters.
You really think that all people do with AWS is host a bunch of VMs and they manage all of the services (databases, storage, big data services, messaging apps) themselves?
I’ve used most of those services and know well that outside of DynamoDB, EC2/Lightsail, S3, DataLakes (s3+athena) and AWS Lambda.
Most of aws services have sub-par performance for insane prices, for components that can easily be replaced at scale with open source more mature components.
Programmers have just lost all of their sysadmin skills these days and will use everything to justify the need for these insane , low performance abstraction abomination that Netifly, AWS RDS, AWS RedisCache, AWS TimeseriesDB, etc are.
Whatsapp used to process billions of users and exited for a billion dollar+ valuation and exit, with just a few FreeBSD running VPSes running their code, and a 20 person employee team…
Most people will never touch stuff in scale of whatsapp, stack overflow, instagram.
and they did it all just fine. Programmers should be mandated to learn Linux and Sysadmin skills again instead of re-inventing entire bullshit services for what is essentially often systemd replacement or a crontab/fcron replacement.
Maybe all of these companies know something you don’t know?
For every WhatsApp that you cite used their own infrastructure, I can site companies like Netflix and Apple that decided to use the public cloud and AWS in particular
> Programmers have just lost all of their sysadmin skills these days and will use everything to justify the need for these insane , low performance abstraction abomination that Netifly, AWS RDS, AWS RedisCache, AWS TimeseriesDB, etc are.
Does it add business value as programmers to spend time babysitting infrastructure? Does it “make the beer taste better”? Does it help to move faster? I can set up an entire highly available data center with all of these services you mentioned with a few lines of yaml/HCL.