Re: ZODB redis/memcache client cache

On Thu, Feb 4, 2016 at 3:30 AM, Rene Jochum <[email protected]> wrote:
> Hi list,
>
> we at Webmeisterei have been discussing a way to have a central cache for
> ZEO Clients.
>
> We think about implementing that as "IStorageWrapper" with the cache code
> from RelStorage and selectable caching backends.
>
> What do you think about that?
>
> I already started with a sceleton of that Project:
> https://github.com/webmeisterei/ZOCache/a
>
> Thanks for your reading and your response,

If your intent is to use this with ZEO, I would focus on providing a
cache replacement.

On a branch I'm working on, I started defining a formal interface for
the client cache:

  https://github.com/zopefoundation/ZEO/blob/asyncio/src/ZEO/interfaces.py

I wonder how NEO approaches caching. For that matter, I wonder how
RelStorage approaches caching. :)  I would love to see the aproach
explained.

FWIW, At Zope Corporation, we decided to avoid the need for a shared
cache by using a content-aware load balancer.

https://github.com/zopefoundation/zc.resumelb

We were able to identify associations between Web requests and data
requirements and segregate requests so that each server had different
and smaller cache requirements.

Jim

-- 
Jim Fulton
http://jimfulton.info

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.