i think the main point to solve this problem is just seprating 'addressing'
and 'hotness'.
'addressing' i used is quite simple, that is 'hash'.
in this case, to balance 'hotness', i'll cut resources into small pieces,
so that resources could be well-distributed and so as 'hotness'.
further more,
Lets assume there are n global caches and since the load is to be
distributed uniformly among the servers and duplicity needs to be avoided,
you need to write a hashfunction f which takes url as an input and returns
an integer value. You can store that url on the cache x where
x = value % n
each ti
approach i have mentioned have flaws . so what other approaches we can try
to solve this ?
On Sun, Dec 14, 2014 at 2:23 PM, SOMU wrote:
>
> 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
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
On Sun, Dec 14, 2014 at 2:04 PM, atul anand wrote:
>
> It is a system design problem .
>
> Suppose a http
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
