5 ms·
Nope. We have an incredibly complicated product, a bunch of actual experts and paid up high level enterprise support. It is about 8x more expensive to run it o
by cryo32 5mo ago
Nope. We have an incredibly complicated product, a bunch of actual experts and paid up high level enterprise support.
It is about 8x more expensive to run it on AWS than it was on actual hardware. And that's using their reference architecture and designs. And the sprawling nature of AWS services and uptake makes it pretty damn hard to get out. We are slowly and quietly migrating everyting to IaaS / kubernetes so we can get it out again. Just moving to kubernetes and packing stuff tight on EKS and thus kubernetes has shaved 30% of our costs off already.
We were sold a lie and fell for it hook, line and sinker.
Edit: also fuck things like Lambda. It's literally the most horrible experience that the universe can muster. Moved most of our lambdas to simple boring http services on top of Go and just leave 20 instances running. Just not having to deal with CloudWatch saved us more money than Lambda could have.
- tacticus 5mo ago> Edit: also fuck things like Lambda. It's literally the most horrible experience that the universe can muster. Moved most of our lambdas to simple boring http services on top of Go and just leave 20 instances running. Just not having to deal with CloudWatch saved us more money than Lambda could have. imagine if instead of being a tied in to aws special interfaces lambda had shown up as closer to cloud run! Though hopefully not the knative style that azure first went with and the LOOOOONG start times.
- cryo32 5mo agoIt'd still suck compared to a completely boring process you can just run on your desktop by ./'ing the executable and looking at the console output. Then chuck it in kubernetes as a ReplicaSet.