I think thats the very essence of AppEngine, that its not like this. It's designed to scale automatically - transparently to the developer. I things should work exactly the same if its running on one 'instance' or 20 thousend.
mangaging seperate 'instances', bringing up more, taking them down some, makeing some dedicated to sepecific roles etc is the lot of work and takes time to get right. So google do it once (drawing a lot on their expeience of doing this on their own products) - rather than everyone designing their own fault tollerent system. On Fri, Oct 3, 2008 at 4:39 PM, cearl <[EMAIL PROTECTED]> wrote: > > There was a posting asking whether App Engine is a VM... > I'm curious to know whether AppEngine...or any other google service > for that matter, supports a paradigm like Amazon EC2, in which users > structure an environment (e.g. I want these four apps running a > particular server) and then then spawn instances of the environments > which support particular classes of applications/tasks. > It seems that AppEngine is more dedicated to the Python application > hosting paradigm, and the environment in which the app runs is more or > less given -- I can run a host off things inside the AppEngine > "container", but I don't necessarily have too much control over the > structure of the container... > C > > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
