We want to implement a "News Channel", where the user can see the messages transmitted by her friends, first figured out the latest message. But the feed must reflect the changes in your friends list . (If she adds new friends, messages from them should be included in the feed, and if she removes friends, their messages should not be included.) If we use the pubsub-test example and attach a list of recipients to each message, this means a lot of manipulation of the message recipient lists when users plug and unplug friends.
First, we modeled the fan-out subscription using normal thinking DBMS. At first it worked, but then, since the IN statement works the way it happens, we quickly realized that we could not continue this path. We found Brett Slatkin’s Presentation over the last years of Google I / O , and we have watched it several times now, but it’s not clear to us how to do this with “dynamic” recipient lists.
We need some tips on how to “think” when modeling this.
python google-app-engine google-cloud-datastore social-networking
Pez
source share