Client/server programming with Java and CORBA
Client/server programming with Java and CORBA
Designing Process Replication and Activation: A Quantitative Approach
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
Object Allocation for Distributed Applications with Complex Workloads
TOOLS '00 Proceedings of the 11th International Conference on Computer Performance Evaluation: Modelling Techniques and Tools
Latency Performance of SOAP Implementations
CCGRID '02 Proceedings of the 2nd IEEE/ACM International Symposium on Cluster Computing and the Grid
Exploring websphere studio application developer integration edition v5
Exploring websphere studio application developer integration edition v5
Efficient development of highly reusable distributed systems using the TCAO
ACST'07 Proceedings of the third conference on IASTED International Conference: Advances in Computer Science and Technology
Real-time compression of SOAP messages in a SOA environment
Proceedings of the 26th annual ACM international conference on Design of communication
| Hi-index | 0.00 |
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.