Monday, February 21, 2011

SOAP/HTTP or SOAP/JMS

SOAP/HTTP
  • For external endpoints
  • Firewall friendly (web services exposed over internet)
  • Supported on all platforms
  • Clients can be simple and lightweight
  • Dynamic caching (to improve performance)
 SOAP/JMS
  • Intranet endpoints
  • Assured delivery and only once delivery
  • Publish and subscribe and asynchronous support
  • Better scalability and reliability
  • Marginal better performance
  • Better support in middleware software
  • Transaction support

No comments: