|
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||
ABSTRACT
The drive towards 'downsizing' from centralized, mainframe systems to distributed systems is based on the expectation of lower costs and greater flexibility from using cheaper MIPS and workstations. The result, however, is a much more complex network of distributed systems, running with a variety of operating systems, database managers, transaction processors, and applications.The author will show that, by using current application design techniques, the cost of deploying and maintaining applications will be higher than ever before and will more than consume whatever benefits may be realized. Application time-to-market, consistency, and flexibility will not improve. A company's Information Systems (I/S) will still be the crucial gating factor in a company's ability to remain competitive.The author will show a specific client/server structuring of the applications (not just the computing infrastructure) that can be the key factor in keeping down the cost of developing distributed applications. This structuring will follow both business process structuring at the highest level and distributed system structuring at the lowest level. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
Peer to Peer - Readers of this Article have also read:
|
|||||||||||||||||||||||||