this post was submitted on 17 Nov 2023
213 points (93.5% liked)

Gaming

3176 readers
581 users here now

!gaming is a community for gaming noobs through gaming aficionados. Unlike !games, we don’t take ourselves quite as serious. Shitposts and memes are welcome.

Our Rules:

1. Keep it civil.


Attack the argument, not the person. No racism/sexism/bigotry. Good faith argumentation only.


2. No sexism, racism, homophobia, transphobia or any other flavor of bigotry.


I should not need to explain this one.


3. No bots, spam or self-promotion.


Only approved bots, which follow the guidelines for bots set by the instance, are allowed.


4. Try not to repost anything posted within the past month.


Beyond that, go for it. Not everyone is on every site all the time.



Logo uses joystick by liftarn

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Trainguyrom@reddthat.com 3 points 1 year ago* (last edited 1 year ago) (1 children)

It’s not a very different pricing model from what AWS does.

That doesn't instill any confidence in me...

[–] EatYouWell@lemmy.world -1 points 1 year ago (1 children)

Paying for the resources you consume instead of paying for capacity you're not using isn't a bad pricing model. Although I prefer HP Greenlake's model over AWS.

[–] Trainguyrom@reddthat.com 3 points 1 year ago

But in the context of consumer product pricing it's wildly anti-consumer to bill a software running largely on your own hardware consuming your own electricity based on how long you run said software. It's expecting consumers to accurately project and plan their usage which consumers are pretty famously bad at. It's also expecting consumers software running on consumer hardware on consumer home networks to function as expected, and all of the three are famously unreliable and janky

The AWS model works so well because of intense automation in horizontal and vertical scaling plus technologies like Kubernetes, Ansible and the entire automated build pipeline. But most importantly it relies on a full team carefully designing the automatic deployment and scaling to maximize benefits and minimize costs