Client-server has multiple intelligent clients which are connected to database on the server. In this environment the application logic will be placed in client software. Client work station is responsible for bulk of the processing, thus consuming most of the system resources and memory. Proprietary database connections were expensive and imposing latency.
In contrast processing in SOA has an explicit functional boundary and related resource requirements. Most of the intelligence has been placed in the messages. There is no fixed processing ratio for SOAs.
Like client-server applications SOA also uses the visual basic and relational databases. However SOA requires that XML data representation architecture along with SOAP messaging has to be established.
In client-server architecture the security is centralized at the server level. Operating system-level security can also be incorporated. That is the data is protected through a single point of authentication, but in SOA the security becomes significantly complex.
The major drawback of client-server architecture is the large maintenance cost. Updating the application code on each client caused high maintenance overhead.
No comments:
Post a Comment