this post was submitted on 02 Aug 2023
49 points (100.0% liked)

196

17222 readers
23 users here now

Be sure to follow the rule before you head out.


Rule: You must post before you leave.



Other rules

Behavior rules:

Posting rules:

NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.

If you have any questions, feel free to contact us on our matrix channel or email.

Other 196's:

founded 2 years ago
MODERATORS
 

I’d like to thank the admins for being so open and direct about the issues that they’re facing.

you are viewing a single comment's thread
view the rest of the comments
[–] thelastknowngod@lemm.ee 7 points 2 years ago (1 children)

To be fair, with a proper autoscaling scheme in place these services should scale down significantly when not in use.

That being said, a big reason for using AWS/GCP is all the additional services that are available on the platform.. If the workload being run isn't that complicated, the hyperscalers are probably overkill. Even DO or Linode would be a better option under those circumstances.

[–] Overmind@lemmy.sdf.org 1 points 2 years ago (1 children)

This. AWS architect here. There are a lot of ways to reduce pricing in AWS like horizontal scaling, serverless functions, reserved instances. Most people aren't aware of it and if you're going to dive in head first into something like cloud, you'll need to bear the consequences and then learn eventually.

[–] greyscale@lemmy.sdf.org 1 points 2 years ago

Even with ASGs, ec2 costs a bomb for performance.

And "serverless" functions are a trap.

If you're gonna commit to reserved instances, just buy hardware for goodness sake, its a 3 year commitment with a huge upfront spend.