Also it appears that moxi could be used as a mid-tier memcache that sits in front of a much larger set of memcache servers. In this case the L1 cache would have proper semantics, as get/set both traverse the same front-end. I could also see this being useful for situations where you have memcache keys being set to a local set of servers (say in one datacenter) and a redundant pool in another data center.
On Sat, Jun 27, 2009 at 6:40 PM, steve.yen <[email protected]> wrote: > > Dustin's described some of the thinking and ideas better than I could > have, but let me just add... > > Jon -- > > Yes, it's in production in one small site now, and a couple of folks > have > been running it in their staging environments, giving invaluable > feedback and surfacing bugs. > > Didler -- > > The front (or L1) cache is very simple right now. You can specify a > front cache size, expiration lifespan and key prefixes. eg, "Cache > only items whose keys start with 'news-sidebar:' and only keep 300 of > them in moxi, and keep each entry for max 50 seconds". It's meant > for hot items that are amenable to replication and temporary > inconsistency. > > best regards, > Steve > >
