Tip 1#
Use coarse grained web services with moderate
size payloads
Tip 2#
Choose correct service (RPC or Document) and
encoding (Encoded or Literal) style for web service
Tip 3#
Carefully design SOAP attachments and security
implementations to minimize negative performance
Tip 4#
Achieve Web services interoperability
§
Web Service implementation in Java: Use
primitive types, String or simple POJO as parameters and return type
Tip 5#
Opt for RESTful Web Services
§
Language and platform agnostic
§
Uses standard HTTP methods to access web
services
§
Need better performance and scalability
§
Much simpler to develop than SOAP
§
Small learning curve, less reliance on tools
§
Could be used when web services are not
sophisticated and there is not need for QoS
Tip 6#
Consider using an asynchronous messaging model
with
§
Slow and unreliable transport
§
For complex and long running process
Tip 7# Use
replication and caching of data to improve performance by minimizing network
overhead
Tip 8#
Use XML compression where the XML compression
overhead is less than network latency
Transmitting attachments such as MRI Scans,
X-Rays, Design Documents and Business Contracts using SOAP messages has become
a common practice.. Optimize transmission of attachments with MTOM & XOP:
References
- http://www.mastertheboss.com/jboss-web-services/web-services-performance-tuning
- http://www.javaperformancetuning.com/tips/webservice.shtml
- http://www.crosschecknet.com/intro_to_mtom.php
- http://www.mkyong.com/webservices/jax-ws/jax-ws-attachment-with-mtom/ - A complete JAX-WS SOAP-based example to show how to use Message Transmission Optimization Mechanism (MTOM) and XML-Binary Optimized Packaging (XOP)
- http://docs.oracle.com/cd/E11035_01/wls100/perform/webservicestune.html
- http://www.ajaxonomy.com/2008/xml/web-services-part-1-soap-vs-rest
No comments:
Post a Comment