←back to thread

WebSockets cost us $1M on our AWS bill

(www.recall.ai)
257 points tosh | 5 comments | 06 Nov 24 18:50 UTC | HN request time: 0.21s | source
Show context
turtlebits ◴[06 Nov 24 19:58 UTC] No.42068395[source]▶
Is this really an AWS issue? Sounds like you were just burning CPU cycles, which is not AWS related. WebSockets makes it sound like it was a data transfer or API gateway cost.
replies(2): >>42068522 #>>42068890 #
1. brazzy ◴[06 Nov 24 20:32 UTC] No.42068890[source]▶
Neither the title nor the article are painting it as an AWS issue, but as a websocket issue, because the protocol implicitly requires all transferred data to be copied multiple times.
replies(3): >>42070045 #>>42070413 #>>42070631 #
2. turtlebits ◴[06 Nov 24 21:51 UTC] No.42070045[source]▶
If you call out your vendor, the issue usually lies with some specific issue with them or their service. The title obviously states AWS.

If I said that "childbirth cost us 5000 on our <hospital name> bill", you assume the issue is with the hospital.

replies(1): >>42071304 #
3. bigiain ◴[06 Nov 24 22:20 UTC] No.42070413[source]▶
I disagree. Like @turtlebits, I was waiting for the part of the story where websocket connections between their AWS resources somehow got billed at Amazon's internet data egress rates.
4. anitil ◴[06 Nov 24 22:37 UTC] No.42070631[source]▶
I didn't know this - why is this the case?
5. Capricorn2481 ◴[06 Nov 24 23:38 UTC] No.42071304[source]▶
Only for people that just read headlines and make technical decisions based on them. Are we catering to them now? The title is factual and straightforward.