Consider using SOAP over HTTP for:
• Externally facing web services (e.g. B2B scenarios)
• For simple point-to-point and stateless services
• Where you need a thin client with no message oriented middleware installations
Consider using SOAP over JMS for:
• when you require high-volume distributed messaging
• Asynchronous messaging
• Where a transaction boundary is needed in the middleware
• Where the message consumers are slower than the producers
• Guaranteed deliver and/or only once delivery of messages
• Publish/subscribe mode
• Distributed peer systems that might at times be disconnected
SOAP Messages : HTTP vs JMS
Subscribe to:
Post Comments
(
Atom
)
Post a Comment