Chatmodule.py Userprofile.py
Sellsomebodysomething.py Makes for great modular code. Tracking the cost of each. Load tester and the functions you are running. I routinely write GAE apps that all they do is run calls to see how much money the other apps cost in a clean room. Real world cost analysis you are right is harder if everything runs on the same account, but really is the cost of your website based on the cost of running chat? I assume you are running chat for community building, so you kind of just put that in the bottom line until you get to a certain size. Remember that every time App1 Fetches from App2 you pay 22 cents a Gigabyte of data. That's likely to be more than the money you would save by deciding chat costs too much. :-) If you write all of your modules as asynchronous AJAX and the data is in silos, then separate apps is not a bad thing. Because no part is actually dependent on the other. From: [email protected] [mailto:[email protected]] On Behalf Of Sanjay Sent: Friday, May 13, 2011 10:06 PM To: [email protected] Subject: Re: RE: [google-appengine] Re: cross app queries 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.
