Hey Sanjay, If you're code is segregated by URL, you can grab your logs to do detailed cost-analysis. The App Engine dashboard also includes some basic information about each URL.
I usually prefer to write small 'library' type modules that I can include in my projects. But, like Brandon said, if the other service is interacted with via AJAX calls and shares no data with the rest of the app it probably doesn't matter (beyond any potential cross-domain stuff). Robert On Sat, May 14, 2011 at 01:05, Sanjay <[email protected]> wrote: > We are still in the process of whiteboarding to decide on overall > architecture of some features, so I was wondering what were the common > patterns used by other developers for modularization. > Writing a chat module (internal to the app) is definately something we are > considering. The case to be made for this is the module can then be > customized to access data more efficiently in other sites since it will have > extra information about the data at hand. Is this the pattern you find > yourself using frequently? > On the other hand, if you write a chat service (or other types of services) > as an external app, it is very easy to determine what each service is > costing you and if it is exceeding your projected budget. Do you have any > guidance on how to do that if you write internal modules? > > -- > 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. > -- 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.
