Not sure what you mean by "in case something happens" - your app and its datastore is served by the same network of servers that serve other apps, so separate accounts won't help, (unless you're going against the Terms of Service, running the risk of having an account banned).
One App Engine account can have 10 apps, each with its own datastore and quota. You could deploy a single app's codebase to multiple app slots, simply by changing the app name in the app.yaml for each instance. That way you could test on a production "test" app or one of your client apps before rolling out updates to your other client apps. You still maintain a single codebase, each client app has its own datastore, and you can control updates. On Dec 20, 2:05 am, GTako <tako.ko...@gmail.com> wrote: > Hi, is it possible to maintain under 1 application, multiple > datastores that each datastore will be as if it is different app > engine account? > for example: i have a web application that should serve 2 companies, A > and B. I would want to open a google app engine account for the web > application files. the datastores for A and B could be 2 different > deployments under the same app engine account or under seperate > accounts. now assume i have N companies. what should i do? > the reason for seperation is that i dont want the datastores will be > dependent and under same account in case soemthing happens. please > advise. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
