PyPi   GitHub

ZEO stores ZODB data in file storage on a server, and serves those objects to ZEO clients, usually web application servers.  ZEO caches data in memory on the server, caches objects in memory on the ZEO clients, and invalidates those caches, when the objects are updated.  

Persistent Client Cache

ZEO cannot only cache objects on the client side, it can store those in a persistent client cache.  That way when the client, the application server, restarts, the cache does depend on the possibly slow connection to the server to warm up. 

Proxy Server Example

Here is an excellent example of using ZEO to solve a complex distributed systems problem.  I wonder if any relational database would allow for this architecture?

I invite you to Register and then link to your own blog postings and software packages..

Powered by Zopache, Grok, Zope and ZODB

Robots Crawl This