All client server architectures are distributed. like ftp, ldap, sql servers are all distributed.
How is the data distributed across many servers in these services? In this case too we have clients which are distributed. Also we can have inteliigent clients which can use different servers based on different servers. In memcached too data is not distributed, that logic is part of client and not the server. On Fri, Jun 11, 2010 at 11:13 AM, Les Mikesell <[email protected]>wrote: > Dilip wrote: > >> Going by that definition: >> >> All client server architectures are distributed. >> >> like ftp, ldap, sql servers are all distributed. >> > > How is the data distributed across many servers in these services? > > > As i understood, in distributed systems there is no single point of >> failure. >> > > Memcache is sort of a special case in that not finding a cached item is not > a failure - it is an expected event and the client is expected to retrieve > the data from the actual source and refresh the cache. If a server fails, > this cache refresh will go to a different server. > > > but in all these cases there are single point of failures. >> >> internet is distributed because there is no single point of failure. >> >> But after looking at the link >> http://en.wikipedia.org/wiki/Distributed_computing, >> here client server architecture is termed as distributed. >> I think the responsibility of not having single point of failure is to >> have intermediary clients, which can do that. >> >> Now I think we can call it that way. >> > > A cache server failure shouldn't have any visible effect other than making > the source servers work harder while the data it held is refreshed onto the > remapped servers. > > > -- > Les Mikesell > [email protected] > > -- Regards Dilip (If you are not living on the edge then you are wasting space.)
