Migrating to Web services - latency and scalability

A common way of deploying Web services is to create proxies that expose the legacy application as a Web service. But when it comes to performance, Web services are facing the same barrage of distrust as any new middleware. Are the critics of Web services right? In this paper we will look at several performance pitfalls that Web services are facing today and at the performance penalties that have to be paid when exposing a legacy application as a Web service. We show results about the latency and scalability of Apache's implementation of SOAP, compare it with the performance of established middleware such as RMI, and look at end-to-end performance of Web services built on top of existing EJB applications.

[1]  Manish Parashar,et al.  Latency Performance of SOAP Implementations , 2002, 2nd IEEE/ACM International Symposium on Cluster Computing and the Grid (CCGRID'02).

[2]  Marin Litoiu,et al.  Object Allocation for Distributed Applications with Complex Workloads , 2000, Computer Performance Evaluation / TOOLS.

[3]  Dan Harkey,et al.  Client/Server programming with Java and Corba , 1997 .

[4]  Marin Litoiu,et al.  Designing Process Replication and Activation: A Quantitative Approach , 2000, IEEE Trans. Software Eng..

[5]  Ada Wai-Chee Fu,et al.  A Gracefully Degradable Declustered RAID Architecture , 2004, Cluster Computing.

[6]  Osamu Takagiwa,et al.  Exploring websphere studio application developer integration edition v5 , 2003 .

[7]  Madhusudhan Govindaraju,et al.  Investigating the limits of SOAP performance for scientific computing , 2002, Proceedings 11th IEEE International Symposium on High Performance Distributed Computing.

[8]  Jerome A. Rolia,et al.  The Method of Layers , 1995, IEEE Trans. Software Eng..