SC Expediter

On the Internet when you search for a particular URL, a directory of known URLs evaluates your request. At some point you either find the URL or conclude that you can't. If the URL is found, routers store the routing information so those subsequent requests can get to the specified URL more quickly.

In enterprise applications, information must also be shared. A single database is one approach to sharing. But no company keeps all its information in a single database. Data will reside on different machines, in different formats and accessible in different ways. But remember, both data suppliers and consumers are constantly changing. So if many applications need access to the same attribute, then each application will have to change if the structure of the objects containing the original attribute changes.

The ShouldersCorp approach tolerates such change.

The SC Expediter maintains a network-based data dictionary along with the routing information required to retrieve the desired data. So any application only has to know the official name of the data attribute. Based upon this name, the SC Expediter fetches the required data in a very efficient manner. All changes within the suppliers or a consumer are accommodated without source code alterations.

The SC Expediter even knows how to transform the requested object into the form required by the requestor.

The SC Expediter stores routes in a cache, which is dynamically constructed upon initial use.

The benefits of using the SC Expediter include the following:

• changes in one application do not require modifications in other programs
• changes do not require programmers to make changes before their new application can be guaranteed to work
• the efficiency of the fetch operation is much better than a lookup operation
• no custom code is required on each screen to retrieve or set data values
• separate facade objects are not required for consumers or suppliers

		© 2007 ShouldersCorp. All Rights Reserved.