Yep, Kaan's idea is very good. Pre-calculating the results and periodically updating them is a great method, but knowing how to avoid stale results, that is, knowing when to run the next dynamic query, is a fine art to make sure users' experience is "live".
On Monday, May 9, 2016 at 3:13:36 PM UTC-4, Kaan Soral wrote: > > "personalized content" is complex regardless of GAE > > I have chronological + geo feeds, for each event, an entity is written for > each person > > Then, that person fetches those entities while digesting the feed > > IMO, whatever you do, you have to pre-process things with GAE, as the > on-request capacity is pretty low, it's not logical to dynamically generate > a feed in a timely manner > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2834559b-f60b-4da4-ba60-d2db22c2368a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
