The only issue is with indexing and access patterns. When tweets are stored individually they can be retrieved by queries referring to individual metadata. This unfortunately is costly. So the question remains, is it OK to retrieve whole sets of tweets compressed together into a Blob in Entity?
On Jan 10, 7:30 am, de Witte <jcreator.xi...@gmail.com> wrote: > 3000 tweets takes about 750 kb, zipped 120Kb, so you can easily store > 20.000 tweets in a single entity. > > Perform any query in memory and you are done. Probably well within the free > quota limits. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
