←back to thread

797 points burnerbob | 3 comments | | HN request time: 0s | source
Show context
DumbStarbucks ◴[] No.36809439[source]
You unfortunately get what you pay for.

AWS is more expensive than God, but I'll be damned if you can't have a throat to choke in less than 10 minutes whenever something like this happens.

replies(4): >>36809597 #>>36809932 #>>36810207 #>>36810334 #
orangepurple ◴[] No.36809597[source]
AWS support replies back to your messages when they feel like it. Their support is just as shady but they have better uptime for sure
replies(2): >>36809668 #>>36809933 #
erulabs ◴[] No.36809668[source]
FWIW, our aws enterprise support reps are available 24/7 and usually respond within a few minutes.

But again, you get what you pay for.

replies(1): >>36810069 #
eropple ◴[] No.36810069[source]
I was working for a pretty big early AWS customer--one that had realized that for the low low price of all your money you could make DynamoDB scale to some truly massive numbers--and one time when we were having trouble around noon Eastern, a colleague called up our TAM. As he told it, the TAM sounded half-asleep, so my colleague asked if everything was alright.

"I'm in Hawaii on my honeymoon and my backup missed your call, so it escalated."

I probably wouldn't have answered the phone. Granted, that's why I don't do that job. But I have always had a real appreciation for the good TAMs ever since.

replies(2): >>36810163 #>>36810261 #
1. silisili ◴[] No.36810261{3}[source]
Weird, I just begrudgingly went from Postgres to Dynamo because it was so much cheaper. We're not huge scale though, so I'm wondering where the costs start to diverge the other way.
replies(2): >>36811103 #>>36813602 #
2. kadoban ◴[] No.36811103[source]
With Dynamo it seems to depend a lot exactly what you're doing. If you're careful about your queries, it's pretty cheap.
3. eropple ◴[] No.36813602[source]
This was, 2012 and we were hitting read and write limits regionally.

It was not a wise plan. It did, however, run. Technically.