Building a system based of distributed objects is not the same as constructing a single object-oriented program. We need to take into account the effects of the network, the fact that we can have tasks interacting while running in parallel, and the possibility of partial failure. Implementing mechanisms to handle failure and coordination of concurrent processes (which will be covered later in the book) may be extremely important; however, the choices we make when designing distributed objects profoundly impacts the performance and flexibility of the system.

It's not enough to take an object model and just distribute arbitrarily, placing objects throughout the network without further consideration. Once we have decided on how to distribute the functionality of the system, we need to spend time and energy defining the interfaces to the distributed objects. Additionally, new users to distributed objects and CORBA commonly encounter problems in identifying the best level of granularity for their distributed objects. Incorrect identification can make the resultant system performance far from satisfactory. Finding alternatives may be too late when you no longer have the time or resources for improvements.

When you initially design your system's distributed objects, you will be concerned with each object's interface, the object model's granularity, and how the complete system is partitioned. The granularity of the object model refers to the scale of abstraction and tasks embodied by the objects and their associated methods.