My app archives and displays tweets in a simple layout, which lets people easily browse older tweets of Twitter users.
This is what happens in a typical user page: - Get 100 more tweets via Twitter API and save to the datastore. Each tweet is stored in a single Entity. - Get 1000 (will be 200 in the real case) tweets from the datastore and display. These datastore reads and writes fill the limits very very quickly. Even a single user (that's me testing) fills the quotas in minutes, checking one or two Twitter user's tweets. I'll use memcache for the reads and that'll help but I don't see my app could serve more than 10 users a day. An idea is to save, say, 100 tweets in a single Entity but that just sounds not right in terms of data structure. How would you store and display tweets (more than 100 a page) in your application? (A typical visitor would like to browse some thousands of tweets.) -- 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.
