Fly.io Postgres cluster down for 3 days, no word from them about it

Re:Fly.io Postgres cluster down for 3 days, no word from the... by eropple on Friday July 21, 2023 @12:40AM (#36810069)

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.

[ Parent | on HN ]

Re:Fly.io Postgres cluster down for 3 days, no word from the... by justinclift on Friday July 21, 2023 @12:58AM (#36810163)

Wonder if that marriage lasted though? ;)

[ Parent | on HN ]

Re:Fly.io Postgres cluster down for 3 days, no word from the... by silisili on Friday July 21, 2023 @01:18AM (#36810261)

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.

[ Parent | on HN ]

Re:Fly.io Postgres cluster down for 3 days, no word from the... by kadoban on Friday July 21, 2023 @03:42AM (#36811103)

With Dynamo it seems to depend a lot exactly what you're doing. If you're careful about your queries, it's pretty cheap.

[ Parent | on HN ]

Re:Fly.io Postgres cluster down for 3 days, no word from the... by eropple on Friday July 21, 2023 @09:38AM (#36813602)

This was, 2012 and we were hitting read and write limits regionally.

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

[ Parent | on HN ]