A benefit of our utilising our underlying stomp and JMS transport is that our service invocations have always been loosely coupled and asynchronous.
One way we are going to be emphasizing this in M4 is to allow the underlying queues to be always available (as long as JBoss is alive) even if the XATMI server is taken down for maintenance or similar. You can monitor our progress here.
For services of this type, no code changes are required, but as tpacall acts just like a distributed enqueue operation, it is advisable to use tpacall/tpgetrply to allow your code the maximum flexibility.
No comments:
Post a Comment