Efficiency Considerations
The first major concern with name resolution is efficiency.
Name resolution uses up system resources, especially with resolution techniques
that require requests and replies to be sent. This means we want to minimize
the number of times resolution is performed, if at all possible. Now, consider
that many people will frequently access the same machines over and over again.
For example, if you go to a Web site called “www.thisisasite.com” for the first
time, your system will need to resolve that name. After the home page for that
site loads, if you click a link to another page on that site, the page will
also be found at that same name: “www.thisisasite.com”. It would be wasteful to
then have to resolve the name a second time.
To avoid this, name systems almost always include some sort
of caching capability, which allows devices to remember recent
name resolutions and retain the mapping from name to address for a period of
time. Whenever a name needs to be resolved, the cache is first checked before
going through the formal process of resolution. The use of caching eliminates
the vast majority of actual name resolution requests that would otherwise be
required.
The drawback of caching is that it requires some system
resources of its own, and that it adds complexity to the system. One issue is
deciding how long to retain data in the cache; if we keep it too short a time,
we generate extra unnecessary resolution requests; keep it too long, and we
risk having the mapping become “stale” if the name assignment for the machine
changes. These are issues that a sophisticated name system must deal with. A
typical solution is to allow each name registration to specify how long
information about that name-to-address link may be cached.
Reliability Considerations
The main concern with name resolution after efficiency is reliability.
As I said earlier in the section, having a name system isn't strictly necessary
for the computers, but it's very important for the users, especially on a large
network like the Internet. While having a single central place that maintains
all information about a name system may make administration simpler, it creates
a dangerous “single point of failure”. If anything happens to the device
storing the information, the entire name system fails.
Modern name systems employ redundancies to prevent having
the entire system rely on any particular device for resolution. A typical
approach in a client/server system is to have multiple servers in different
locations (or attached to different networks) that can respond to name
resolution requests.
No comments:
Post a Comment