Shouldn't we make a single application server (and clone of it using a common config server for load balancing)? As done with sharded/distributed databases.
Just one application server. I guess it can be easily done with the present model but for new people/ movers from conventional model, would be more convenient. Also, if using many clients it would be wise to have a single entry point to the backend cache. Changing the server list on all clients could be a pain. -- Regards, Neeraj Agarwal On Sat, Aug 27, 2011 at 12:46 AM, dormando <dorma...@rydia.net> wrote: > > Hi everyone, > > I'm new to memcached. Here's my question: > > When we are configuring clients with memcached, we enter server addresses > running memcached in our client application. > > Our servers; S1, S2, S3, S4 > > Clients: C1, C2 > > > > Now suppose for C1, we give memcached servers as S1, S2, S3 > > for C2: S2, S3, S4 > > > > Now we give key1 to C1 to store. > > And query for same key1 with C2. > > > > How would it behave? > > C1 would store on Sx and C2 would store on Sy, which will likely not be > the same host. > > All clients must have the same exact server list, in order to store keys > in the same places.
