Hey App Engine team, I was wondering if you could share a quick high-level summary of how the app engine deployment works internally? I've been trying to figure out how it works so as to mimic the behaviour for my own framework...
All the ways that I can think of are nowhere near the elegance of what App Engine offers: * Using a SAN for the app code and putting the code into versioned directories. Whilst simple, this has the downsides of cost — both in terms of money and latency. * Using something like Capistrano/Fabric to do parallel updates to many servers. But this doesn't really scale so well and requires a lot of administrative overhead. * Putting the app code into a distributed data store. But this has the downsides of having to do a datastore lookup before serving every request — not to mention the additional time it takes to get the code for a cold start... Would love to know how you guys do it — thanks! -- love, tav plex:espians/tav | [email protected] | +44 (0) 7809 569 369 http://tav.espians.com | http://twitter.com/tav | skype:tavespian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
