Hi, Splitting your app into multiple services that are isolated seems like a good architectural decision. For instance, I want to implement in-window chat on the website I am building on AppEngine. Since this website is probably the first in a series of apps I am going to be making for a customer, I think it would be nice if I could write the chat functionality as a standalone app/service that is used by this app, and possibly in the future by other apps.
Also, writing apps as a set of services glued together seems to be a good way to go, because users data would be better isolated. For instance, if a bug in the chat service code exposes user data, it would only have access to the local datastore and therefore only be able to read chat history as opposed to getting full contact details for every user of the website. I have 2 questions: 1) What do people think about architecting a complex website this way? 2) [More for a Google Engineer] If I use urlfetch to access other appengine apps (for the reason I mentioned above), since it can remain inside Google's infrastructure, is it more efficient than urlfetches to external sites? -- 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.
