How about this: 1. Rely on an in-memory implementation of FIFO as the primary storage. 2. Store stuff to memcache as a temporary backup to protect against your front-end instances dying because of over-usage of memory, or other reasons. 3. Memcache writes should probably be asynchronous (use taskqueues) to avoid incurring unnecessary latency (I think taskqueue.add is faster, but you should try it out) 4. If your client B doesn't read from the FIFO for some period of time, say 60 seconds, back up your FIFO data into Datastore (asynchronously of course).
On Sun, Dec 11, 2011 at 11:27 PM, Brandon Wirtz <[email protected]> wrote: > Memcache won’t work by itself. DataStore writes would make this expensive > for what you are looking to do.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Grigory Fishilevich > *Sent:* Saturday, December 10, 2011 12:40 PM > *To:* [email protected] > *Subject:* [google-appengine] Remote realtime FIFO implementation**** > > ** ** > > Hi all, **** > > ** ** > > I'm new to Google App Engine and I'm looking for an advice. **** > > ** ** > > I want write a remote FIFO for realtime access outside of GAE. **** > > This FIFO should contains small integers only and works as follows: **** > > - client A write integer-values to FIFO**** > > - client B reads the values 1-5 seconds later**** > > - after what the values are invalid and can be deleted**** > > - there are always only 2 client per FIFO**** > > - it should be possible to have x FIFOs in the app**** > > ** ** > > Importent for me: ability for realtime and concurrency, no deadlock etc. * > *** > > ** ** > > So, I'm new to GAE, wich service can I use for my App? **** > > Pull Queues are limited to 100 active queues, it's not enough for me. **** > > ** ** > > Should I use memcache? DB? **** > > ** ** > > Thank in advance**** > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/aEVQATdRwkQJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en.**** > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
