Distributed Architecture

To achieve the highest level of performance in request processing, the system architect must turn to Distributed Systems. The general idea behind this type of architecture is to divide (i.e., distribute) the processing of information amongst a number of specialized servers that perform different types of processing concurrently.

The first step in this direction is usually to create business objects (components) to divide the presentation, business, and data services. To achieve the highest performance, the system can use Microsoft Transaction Server to control the processing of business objects.

This approach results in increased performance, better resource sharing, and increased maintainability.

Further performance gains can be obtained by using Message Queue Servers. This architecture enables asynchronous communication between the client and server components. The benefits of this architecture are load balancing, increased performance, and improved resource sharing.

See also:

• Desktop and File Sharing Architecture
• Client / Server Architecture
• Web based Architecture