> Pushing calculations from read time to write time makes sense in that reads > seriously out number writes for most web applications.
Pushing calculations at write time instead of read time has some other very very strong implication that you're probably missing: that you know in advance what you want to calculate. For very narrow application domains this is probably true. In the business environment it's often not know, and the flexibility in this regard provided by relational databases is part of what has made them so popular. For Google own apps this is not probably a problem, since they have other means of processing massive amounts of data. If your only window to your business knowledge is accessible via GAE, you're in a serious problem each time your requirements do not fall into the realm of what you anticipated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
