Component Design for Relational Databases - High-Performance Web Databases: Design, Development, and Deployment - page 388

Exhibit 25-4. One-to-one component to subdata model example.
DATA-COMPONENT GRANULARITY CONSIDERATIONS
To prevent proliferation of components, the granularity of the compo-
nents can be increased. For example as shown in Exhibit 4, use case U1 and
U2 use sub data models M1 and M2 correspondingly.
Instead of having components C1 and C2 that correspond to use cases
U1 and U2, if U1 and U2 are closely related, a single component C (with
interfaces I1 and I2) can serve U1 and U2, as illustrated in Exhibit 5.
The same exercise of combining related use cases into components
could be carried out through the application design space thereby bringing
component proliferation under control.
IMPLEMENTATION OF THE COMPONENT-BASED DESIGN USING
MICROSOFT'S ARCHITECTURE
Even though the component technology war between CORBA and DCOM
is far from over, the fact remains that DCOM (in some form) has been
around longer and is used widely in the industry. It also has, arguably, more
opportunities to mature into a stable industrial strength technology. Con-
sequently, Microsoft's DCOM platform is discussed in the implementation
of the data-component approach illustrated in Exhibit 3.