Do you mean that it's still the case that more resources are allocated than actually used or that the code does not need to be optimized anymore due to elastic compute?

[–] 1984@lemmy.today 9 points 1 year ago* (last edited 1 year ago) (1 children)

I think both are consequences of the cloud.

It's cheaper for companies to just add more compute than to pay devs to optimize the code.

And it's also not so important to overpay for server capacity they don't use.

Both of these things leads to AWS making more money.

It's also really good for aws that once these things are built, they just keep bringing in money on their own 24 hours per day.

[–] brennesel@feddit.de 2 points 1 year ago

If I remember correctly, that was the original idea of AWS, to offer their free capacity to paying customers.

Do you think that AWS in particular has this problem or Azure and GCP as well? I have mainly worked with DWHs in Snowflake, where you can adjust the compute capacity within seconds. So you pay almost exactly for the capacity you really need.
Not having to optimize queries is a good selling point for cloud-based databases, too.

It is certainly still cheaper than self-hosted on-premises infrastructure.