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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
