"Sessions" with Google Cloud Endpoints
google-app-engine, google-cloud-endpoints, java, rest, session
Solution
The datastore is pretty quick especially if you do a key lookup (as apposed to query). if you use NDB then you will have the benefit of auto memache your lookups.
Problem
This question is only to confirm that I'm clear about this concept. As far as I understand, Google Cloud Endpoints are kind of Google's implementation of REST services, so that they can't keep any "session" data in memory, therefore: - Users must send authentication data with each request. - All the data I want to use later on must be persisted, namely, with each API request I receive, I have to access the Datastore, do something and store the data again. Is this correct? And if so, is this actually good in terms of performance?