This is, essentially, precisely what memcached is. You can view memcached as one large, shared map that should appear identical to all clients as long as they are configured the same. It isn't "one object," but rather a distributed cache shared equally amongst all the servers running the daemon, but from the point of view of the clients/code, it basically looks like one large map.
On Wed, Sep 29, 2010 at 12:18 PM, parsa <[email protected]> wrote: > Hey fellas, > > I have a large key-value map that I want to serve in a web service > application. I want to keep a single instant of this map inside the > memory (around 600mb footprint) and let every request that is made to > the service use the very same object. I'm new to memcached and to be > honest, caching in general. So is it better to keep the object in the > memory as a whole or to add key-values to the cache separately? (btw > I'm using Scala on Lift) > -- awl
