2 ms·
They conveniently provide no detail about the usecase, so it's hard to tell But, yeah, there's certainly a solution to provide better performances for cheaper,
by wiether 1y ago
They conveniently provide no detail about the usecase, so it's hard to tell
But, yeah, there's certainly a solution to provide better performances for cheaper, using other settings/services on AWS
- adamcharnock 1y agoWe're hoping to write a case study down the road that will give more detail. But the short version is that not all parts of the client's organisation have aligned skills/incentives. So sometimes code is deployed that makes, shall we say, 'atypical use' of the resources available. In those cases, it is great to a) not get a shocking bill, and b) be able to somewhat support this atypical use until it can be remedied.
- wiether 1y agoThank you for the reply I'm honestly quite interested to learn more about the usecase that required those 50k API calls! I've seen a few cases of using S3 for things it was never intended for, but nothing close to this scale