> 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.
I'm not really sure what you're talking about anymore. Why do you think there's a problem with giving each client the same server list? What's so hard about that? Clients issue requests *directly against servers*. The entire point of this system is to create a large, fast, scalable, shared cache between *all of your application servers*. The *only* thing you have to do is to use the same server list among all your clients. The rest is magic, and it's awesome magic. Don't resist it. -Dormando
