11–20 of 129 posts
Why would anyone put anything production critical on Google these days, knowing that they provide 0 support across most of their business?
Why would anyone put anything production critical on Google these days, knowing that they provide 0 support across most of their business?
because we're paying customers? my bill is peanuts, but i know there are many big customers, e.g. Khan Academy. and also they have Premier Support which is $500/mo.
Why would anyone put anything production critical on Google these days, knowing that they provide 0 support across most of their business?
because we're paying customers? my bill is peanuts, but i know there are many big customers, e.g. Khan Academy. and also they have Premier Support which is $500/mo.
Khan Academy may have it easier, I'm sure Google won't let them down
Really, go somewhere else, spend less money and have better support.
(At the expense of, if you're lucky, Google will give you almost zero headaches)
" Upgrading to HRD will solve your issue. M/S is deprecated and there is a clear and straightforward path to migrating to HRD." Can anyone explain why this is not possible for them? Wonderful Google support apart, there are a lot of alternatives out there.
Multiple comments mentioned that this occurs in HRD as well.
Why would anyone put anything production critical on Google these days, knowing that they provide 0 support across most of their business?
I would recommend trying your apps on OpenStack (Openshift in particular), which doesn't have the vendor lock-in, which you face right now.
Why would anyone put anything production critical on Google these days, knowing that they provide 0 support across most of their business?
Well, the bug report doesn't really invite quick attention. Simply reporting your observations is not enough: you should position yourself as a competent customer, by explaining what you have done to ensure the problem isn't on your side. Mention the code hasn't changed, that you have no database cleanup cronjobs or similar running that could be interfering, etc. My first instinct when I see a report like this is: he…
It looks like OP of the bug-report is using a depreciated feature/program which according to the Project Member is causing latency issues at a specific time daily. But that could not be the real issue since another commentator who is using the new HRD is also having the same problem. It is even frustrating for people who are reading this. All it implies is the lack of communication from Google when something goes awry. Come on Google, stop reinforcing my stereotypes about your customer support!
Selling to a customer is different than selling to a business, you may have a great product at a great price but if you offer terrible CS, in the B2B world everyone is going to avoid you. It is a place where support is valued more than the product itself.
Therefore, unless you start offering a decent CS, you can lower your price all you want, I will be sticking with AWS.
I'm sorry, but this is the price you pay for running your business that is dependent TOTALLY on a 3rd party service. Forget Google, everyone out there is most likely the same, that's why it's important for you to run your 'apps' on something you have control over - Like Linode, AWS, Rackspace, Openshift, etc. and also have back-up nodes from other providers for redundancy, for emergency situations, incase of storms,…