Scaling of Naming/Binding mechanisms.

The scaling of different location services must be considered in terms of number of messages required to locate a given service as well as in the usual scaling of software. Clearly a single central naming/binding service scales well for messages, but rather poorly for performance since it would be inundated with messages. Multicasting for the service (i.e. the opposite extreme of full distribution) may be expensive in network traffic, but is mediated by caching results. As we shall see with directory service work, something in between is usually the correct engineering choice.