It's an interesting issue...I think we're all happy for things to behave pretty much like a black box when stuff is working as it's meant to, but are we so happy with that when things aren't working?
Personally I don't need to know who specifically is responsible for the machines my apps run on, to be able to contact them directly etc. And I don't think that's really a viable option. However, I agree more feedback on causes and fix schedules when things go south would be good, along with frequent updates. I think 'naming and shaming' Google on infrastructure let downs, on your app, would be an option for you too, to lay the responsibility with Google. Significant issues, particularly on popular apps with decent visibility, are surely embarassing for Google given their reputation. Serving them a dose of that embarassment by telling your visitors 1) we're Google's infrastructure, 2) they're having problems right now, would probably give Google more incentive to avoid repetition of these issues.. :) If a number of popular apps were frequently reporting issues with Google, word about that would get around. >From listening to talks from GAE folk though, I get the impression stability is of paramount importance..so I'm hopeful issues like those recently will be exceptions. On Mar 6, 2:24 am, dsw <daniel.wilker...@gmail.com> wrote: > I have long wanted to build apps on Google App Engine and have learned > a lot about it in preparation for doing so. However the one problem > is if I have a customer and their app goes down for an hour and they > call me and say "what happened?" and "how can we prevent that in the > future?" my only response will be "I don't know" and "we can't." > These are unacceptable answers. > > If you want App Engine to "cross the chasm" and become really for real > then at the very least what you need to do is provide the kind of > depth of sight into your infrastructure that you the Google engineers > have. Further you need some kind of locality in the cloud: it would > help if there were some way of ensuring reliability by knowing that > (1) I have bought space on some particular cluster of machines (2) > which is now stable and more apps are not being added to it; I should > know (3) who is maintaining that cluster and (4) be able to send them > a trouble ticket and (5) have some idea of what is wrong and how long > it is going to take them to fix it. > > This opaque cloud utility of compute stuff is a fantasy: some locality > and transparency will be needed or App Engine will never be really for > real. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
