> > The problem with that is that if any of the sub-aplications > > get too complicated or too much traffic, it will affect > > all.... > > The main point of App Engine is that your apps will scale regardless > of the traffic (if written correctly). All your sub-applications can > reside under one GAE app and scale appropriately. > So you lump application instances designated for different organisations into a single application id (or instance). Yes, big table is amazing but lumping data from disparate organisations and forcing the application to search an artificially large database is ridiculous.
Not to further mention the complexity of building and maintaining such an application; with very real risks of cross-exposing organisation data because of software bugs. All these because of TOS 4.4 ? IMHO, absolutely silly. look at the following clarification which I made earlier, http://groups.google.com.sg/group/google-appengine/browse_thread/thread/84806609ffe2617c/5ad4d25338709667?lnk=gst&q=tankh64#5ad4d25338709667 > > and the quota will be reached really faster, although there are 'many' > > sub-aplications nearly independent of each other.... > > The TOS prevent developers from aggregating the free quotas across > apps to serve a web app. There's a gray area here which only Google > can decide. For example, if you did a Google Docs app would that be > "independent" of a Google Spreadsheet app? > AppEngine must adopt the concept of application instances; each instance with its own database context and scope. Then aggregate and account all the resources consumed under the same application id; but allow accounting info for each instance thereby allowing us to account the same to our customers. TOS 4.4 makes investment very risky for developers who basically requires an application instance tied to an organisation. Appengine (and its TOS) is very much geared towards deploying a single application id (instance) meant for the world as one community. Given that appengine is a closed system and a TOS 4.4 that can basically yank your deployment, think carefully and at least get approval first before committing to it. Again, see http://groups.google.com.sg/group/google-appengine/browse_thread/thread/84806609ffe2617c/5ad4d25338709667?lnk=gst&q=tankh64#5ad4d25338709667 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
