We also use App Engine for our game content, and in our case, all our game data is just stored in Python modules. In 'code' as you will. An advantage of this is that you can easily send game data back just from instance memory.
For us the increase in startup time is negligible, although I do not have experience with Java. My impression would be that this approach should work fine for few thousand constants. On Thursday, June 9, 2016 at 5:20:03 AM UTC+2, YuRen Lin wrote: > > Hi, all > > I am in the game industry and use Google App Engine as my backend server. > My problem is we do the game logic calculation in the server side and use > thousands of Constants which read from csv files. Our current solution is > to read CSV files and store them into the datastore. Then when a request > comes, the servlet checks memcache first, if miss read from datastore. This > is done automatically by Objectify. I am wondering if there is other more > effective way to do this. > > Other solutions include: > 1. store all constants in the servlet as int array. But I think the launch > overhead may be a lot, since there are thousands more constants. > 2. read constant from csv files each time the servlet needs it. I don't > think this is a good idea. > > > Thanks in advance. First time to post here. > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/5e7bfa3d-b064-4f9d-b850-c771d6af299d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
