On Tue, Dec 17, 2013 at 8:04 PM, <[email protected]> wrote: > I'm after a bit of advice on how best to structure a GAE application. > For this application, the frontend instances in GAE will take external > requests, and in turn I need to log strings from all instances to a central > location - ideally just a flat file, as there is no requirement for > NoSQL/SQL and the write operation needs to be as lean/quick as > possible.Storing each line in NoSQL seemed overkill... > > So I figured I'd ask to make sure I'm not missing something obvious, as it > seems to be a common and basic use case. Ultimately the application may use > map/reduce to take the file/files and post-process them if that helps in > the equation. > >
I would write the strings straight into standard logging, then set up a cron job to regularly extract the information you want from logs using the Logs API: https://developers.google.com/appengine/docs/java/logs/ . It's fast, lean, and extremely dependable. Plus it's a fairly cheap option compared to the cost of using a database to store the information. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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. For more options, visit https://groups.google.com/groups/opt_out.
