KPMG Survey Highlights Outsourcing Opportunity for Lviv
Document Actions
Zope at Google AppEngine
GAE exposed a challenge to run Zope in severe environment
When Google released GAE, a lot of folks in Zope world turned their sights to Google because Python, the heart of Zope was the language GAE was talking in then. Preliminary experiments showed that Zope and namely ZODB, persistence machinery behind Zope had little chances to survive at GAE. Folks succeeded into porting component architecture there, in running with non-ZODB storage, and in many other initiatives.
We set the goal high: Run Zope3 at GAE with ZODB and persistency. After 9 month of growth together with GAE, its SDK and service we've had basic zope3, worldcookery and grok' adder running at Google. We've learned a lot about GAE at its limits, were puzzled with a lot of obscure moments. Experienced unexpected and unreported kills. Rewrote launch and processing machinery several times.
There are many details to what was accomplished and how it was accomplished, you can see some from slides below. Zope3 is far from being production ready for GAE, but it works! We've even came with quick-n-dirty buildout that transforms Zope into GAE deliverable with single bin/buildout. Comments are welcome.
Topical discussion at http://chatterous.com/zope-gae.
_____tags:
