On Thursday, June 6, 2013 5:27:59 AM UTC-4, Mohammad Al Quraian wrote: > > I'm just starting with GAE, so bare my ignorance. My app is using a > in-memory list that is accessed very often by font-end clients, my solution > before was to use a static list. After gaining more info on GAE I know now > that this wont be good because each instance would have it's own list > (right?). > So, are backends the best fit for that? Is there another solution? > The issue is the the backend has to be up throughout the app lifetime, > just for holding a simple list that is not even that big. Would that be > costly $wise? >
if the list is not that big, then maybe its ok to keep in memory on each instance. the F1 instance type has 128mb of ram. you can choose bigger instance sizes too. if it doesn't fit, then you could store it as rows in the datastore and query against it. you could also use memcache, but each key+value must be less than 1mb. so you would probably have to break it up into smaller pieces like you might if you put it in the datastore. backends would also work, its kinda the same thing as keeping it in memory on a frontend instance, except that you can scale them independently of your web traffic. so the choice would depend on your traffic patterns and whether you want to add that complexity to your app. --alex -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
