MOM Vs RPC
|
Feature |
MOM |
RPC |
|
Metaphor |
Post-office like |
Telephone like |
|
Client/Server time relationship |
Asynchronous. Clients and Servers may operate at different times and speeds |
Synchronous. Clients and Servers must run concurrently. Servers must keep up with clients. |
|
Client/Server Sequencing |
No fixed sequence |
Servers must first come up before clients can talk to them. |
|
Style |
Queued |
Call-Return |
|
Partners need to be available |
No |
Yes |
|
Load-balancing |
Single queue can be used to implement FIFO or priority based policy |
Requires a separate TP Monitor. |
|
Transactional Support |
Yes (Some Products) Message Queue can participate in the commit synchronization |
No. Requires a Transactional RPC. |
|
Message Filtering |
Yes |
No |
|
Performance |
Slow. An intermediate hop is required |
Fast |
|
Asynchronous processing |
Yes. Queues and triggers are required |
Limited. Requires threads and tricky code for managing threads. |
