I’d like to thank the admins for being so open and direct about the issues that they’re facing.
this post was submitted on 02 Aug 2023
1001 points (100.0% liked)
196
16552 readers
2813 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Yep. And if you want to really save some cash and don't mind getting a little crazy, use an EKS node orchestrator that supports spot instances. I'm starting to do a serious dive into Harness at the moment actually.
Google recently released a white paper on cost saving in kubernetes as well.
If you've got a kubernetes cluster running on 10 different spot instances, isn't there a risk that all ten could be revoked at the same time? Even if they are built out across regions and availability zones?
Counterargument: I don't need Lemmy to have 100% uptime. It's not a corporate service and while -- obviously -- if it's down all the time I would eventually move on, I'm not going to fault a not-for-profit entity for periodic failures.