Tim,
It really depends on what you're doing. One of the challenges of developing
on a distributed store like the App Engine data store is adjusting the way
you approach persistence for objects. For instance, suppose you store
favorite colors per application user. The canonical way of solving this
Ikai,
This is not really a relational data question. It is a summary data
question. To give a brief overview on my approach; here is the history
over the past 20 years on my approach to summary information:
1. Calculate the summary information on the fly per user request.
Very data
I like the concept of MapReduce, however, I think it might be easier
to borrow a page from Apple with the Grand Central Dispatch released
in Snow Leopard. The hardest part would be implement a usable tool /
framework in Java which many developers could leverage and understand.
Especially, in my exp
Thanks for the feedback, Tim. It sounds to me like what you are looking for
is MapReduce support. There's an feature in our issue tracker for this:
http://code.google.com/p/googleappengine/issues/detail?id=112
Map/Reduce would be a great fit for our model since the work could be
transparently dis
I agree that developing for concurrency is incredibly difficult, though I'm
of the opinion that Map/Reduce is powerful because of its accessibility.
It's certainly not trivial to try to reduce a computation of a large dataset
to Map/Reduce, but my hope is that as the feature becomes available, we'l
