4 ms·

We filed a more concise bug report too: https://code.google.com/p/googleappengine/issues/detail?id=8881 https://code.google.com/p/googleappengine/issues/detail?

by thijser 14y ago

We filed a more concise bug report too: https://code.google.com/p/googleappengine/issues/detail?id=8881 https://code.google.com/p/googleappengine/issues/detail?id=8... This is a daily outage that affects all our master/slave appengine applications. We know these applications are 'deprecated', but we're still paying significant money for the service and therefore hadn't expected 'deprecated' to mean 'won't be fixed when there are problems'. Migration to HRD is not trivial even with the tool provided by Google. HRD has a different consistency model, blob keys and associated image serving URLs will change by migrating, and last time we checked any deletes that happen during migration (which can take days) will not make it into the migrated app.

brudgers 14y ago
Shedding responsibility for problems arising from continued use is pretty much the essential rationale for deprecating a piece of software. Google has never appeared particularly concerned about backward compatibility or facilitating small segments of its customer and user bases.
- mark-r 14y ago
  "Google has never appeared particularly concerned..." seems to be a recurring theme. The company was designed to work at large scale, and individual problems don't get the attention they would at more customer-oriented companies.