Take the 2-minute tour ×  I was wondering about implementing my
own sessions (more for an exercise than anything else) for a GAE
app I'm working ... at first I was thinking of using the
datastore to store the session data. However, every time
something needs to be added to the session 'bucket', it would
require saving to the datastore. Obviously that's bad since we
want to minimize our writes. Then I thought about using memcache
... seemed like a good idea but then we're faced with issues of
possible session corruption due to memcache being "evicted
through memory pressure" by Google. So does that mean we are
left with only the following options:    1. Storing all session
data in cookies   2. Writing all session data to datastore and
memcache, and then only reading from memcache  Anyone have any
other ideas?  share|improve this question add comment  3 Answers
up vote 3 down vote accepted  I suggest checking out (and
contributing to) these three implementations of appengine
sessions before rolling out your ow