Hacker News new | ask | show | jobs
by lokar 29 days ago
My company also used all 3 (at a very large scale / spends). MS was nice, but useless / incompetent technically. Anything non-trivial took forever to get a straight answer or resolve. We rarely got to speak directly to anyone with real expertise.

AWS, we could speak directly to Sr engineers on the relevant team. Full transparency, highly responsive. They were clearly trying to understand our issues and suggest change for both us and themselves.

Google was mostly useless. There was one team I got to talk directly to, who were great. But that was the exception.

1 comments

My experience with AWS hasn't been good when we had major problems in redshift becoming unresponsive. Since it was an intermitent issue and not a full blown blackout they just shrugged and we kept having problems for months.
I can confirm. Redshift support is mediocre even for a F100 firm with TAM support if the workload is large and complex and you have some needle in the haystack causing problems like you allude to.

Practically speaking keeping an eye on locks and transactions is a good idea, as is watching out for your statistics on key core columns going bad when they shouldn't. (analyze and vacuum sometimes don't actually do anything when you need them to...)