4 ms·
Honestly. I would ignore any comment that is that old. Running anything on AWS or Google 3 years ago. That must have been hell.
by user5994461 10y ago
Honestly. I would ignore any comment that is that old.
Running anything on AWS or Google 3 years ago. That must have been hell.
- vgt 10y agoI'll add that the main issue seems to be with Google AppEngine of two years ago. For compute options Google Cloud has Compute Engine, Container Engine (Kubernetes), and even AppEngine Flex Environment these days. (work at Google Cloud)
- saurik 10y agoThe attitudes and competencies of organizations generally doesn't change over the time scale of only a year and a half (which is really not long at all... I mean... I've been using AWS now for over eight years and had a product deployed on App Engine six years ago; the people I work with who really like GCP have been using it for three or four years, and our conversations about it and their experiences track that far back: a little over a year is nothing...), and when it does it is generally due to a massive disruption, such as a changing of the guard at the upper echelons of management. This is particularly true of companies that are dominated by personality effects, as are most of these massive tech companies. FWIW, the serious complaints I would lodge against AWS today are the same things I was complaining about back in 2009 on the Amazon EC2 forums. Sure, the actual technical abilities of products change over a year and a half, but that is neither the complaint of this comment thread here, nor of the one I linked. Let me put it another way: the key issues people have with Google are generally issues that happen over longer scales of working with them: things are great for a half a year or even two or three years, and then the rug gets pulled out from under you (whether or not you are paying for the service and whether or not you are generating lots of revenue; I mean: look at the fate of Google Wallet); if you seriously are throwing out experience from as recently as a year and a half ago and seriously believe that after three years knowledge would have become fundamentally out of date, your article today about "use Google, not Amazon" is clearly also worthless as the real question users need to answer for themselves is "in three years will I have regretted my decision", and you believe articles and comments and experience (such as yours!) is not capable of guiding people, which is ludicrous.
- user5994461 10y agoAgree that the general criticism didn't change. (And the criticism from that link was on AppEngine, so that's certainly on point). However 1-3 years is a big gap in terms of capabilities and tooling. If I go back long enough ago, there was a time without nat instances, without VPC, without region in X zone where I have customers. That's deal-breaking changes. Some things we use today to manage our servers didn't exist or didn't support a specific usage some months ago. I'm certainly biased because I've only been using AWS since last year. I see the things we do which are marked as "added MM-YY" and it would have been hell to try to do that 3 years ago. That's why I advise to take old criticism about capabilities with a grain of salt.