Hi Single user model and probably namespaces for each application, if each application where to run in the same instance. If each application used the same code in different application instances then namespaces are possibly not relevent,
I think you should do some more reading about the fundamentals of appengine, as questions like "so that the applications may be load balanced over servers easily maybe?" suggest a bit of a gap ;-) Have a look at http://code.google.com/appengine/docs/python/multitenancy/overview.html for more about namespaces. Also you should mention if you're interested in java or python so appropriate docs can be pointed to for concrete examples/api Rgds Tim On Nov 2, 12:02 pm, Kaan Soral <[email protected]> wrote: > I was thinking, > > Lets say I will have 1.000.000.000 users on 100.000 applications. > > So there are 100.000 applications that use the same code. > > Should I give every application its own Model to store users (Lets say > 10000 users), so that the applications may be load balanced over > servers easily maybe? > > Or should I just use a single Model for 1.000.000.000 users? -- 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.
