

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?


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?
Coming from Germany, I don’t know if the traditional way to eat muesli is just adding yoghurt. Most people I know normally add fresh milk to it.
Personally, I enjoy my daily Müsli with vanilla soy milk (but I tend to be the only one liking that), fruit skyr (or yogurt), some oatmeal and/or crunchy granola, and most importantly, at least two kinds of fresh fruit, like bananas, peaches, apples, pears, or grapes. Without fruit, it just tastes bland.


Beer is always good! Source: I’m German


Exactly. Maybe I’m sounding awfully optimistic, but I actually enjoy the slow pace here. Posts can be 1 week old and there are still comments popping up after a while. It also makes interactions more meaningful in a way.
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.