another one could be some sort of hashing logic modulo n. Get request, create hash , compute modulo n. check assign cache and return. This will make sure of even distribution but with additional cost of hash computation.
Regards, Vikash 8121873513 On Sun, Dec 14, 2014 at 5:07 PM, <algogeeks@googlegroups.com> wrote: > > algogeeks@googlegroups.com > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/algogeeks/topics> > Google > Groups > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > Topic digest > View all topics > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/algogeeks/topics> > > - Distributed System problem <#14a489759ff4211e_group_thread_0> - 3 > Updates > > Distributed System problem > <http://groups.google.com/group/algogeeks/t/a74720cc5f28f8b?utm_source=digest&utm_medium=email> > atul anand <atul.87fri...@gmail.com>: Dec 14 02:04PM +0530 > > It is a system design problem . > > Suppose a http request is sent to server . Now Server maintains cache for > fast retrieval . if link is present int the cache then it just takes a data > from cache and return it to user but if not , then user will fetch that > http address and then store it in its cache and return same to the user . > > Problem is that there are many server and many global cache as expected in > distributed system. Now when request is received by a server then how can > we maintain global cache such that server can know which cache to query > instead of querying each global cache as it will be inefficient. > > one approach can be...... maintain 26 global cache . Now when request is > received by server it check the web link say , www.*a*bc.com ... here > server will query cache-1 . Similarly cache-2 will take care of links with > starts from "b"...www.*b*bc.com ....and so on.... > > above method will avoid duplicity in caches but will not be very efficient > as a cache may have higher query rate than others... > > > any other approach ?? > SOMU <somnath.nit...@gmail.com>: Dec 14 02:23PM +0530 > > Then the Domain name is altered from abc to bbc .. That indirectly means > that the nameserver will change. > > So in that case the Cache will point to the New NameServer .. > > Thanks, > Somnath Singh > > atul anand <atul.87fri...@gmail.com>: Dec 14 02:29PM +0530 > > approach i have mentioned have flaws . so what other approaches we can try > to solve this ? > > Back to top <#14a489759ff4211e_digest_top> > You received this digest because you're subscribed to updates for this > group. You can change your settings on the group membership page > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/algogeeks/join> > . > To unsubscribe from this group and stop receiving emails from it send an > email to algogeeks+unsubscr...@googlegroups.com. > -- You received this message because you are subscribed to the Google Groups "Algorithm Geeks" group. To unsubscribe from this group and stop receiving emails from it, send an email to algogeeks+unsubscr...@googlegroups.com.
