Hi again,
When dealing with TIBCO products you can easily get confused by many related buzz words or methodologies.
I've decided to write a brief comprasion.
I've decided to write a brief comprasion.
Rendezvous | JMS | |
Radio broadcaster | Telephone | Real-life example |
Yes | No | Sending messages to all clients |
No | Yes | Requires server |
No | Yes | Persistence |
No | Yes | Reliable messaging |
Yes | No | High-Speed messaging |
- | Yes | Clustering & Failover |
Topic | Queue | |
Publish/Subscribe model | Point-to-Point model | Architecture |
Multiple clients subscribe to the message | Only one consumer gets the message | Number of clients |
No | Yes | Messages sent by order |
No | Yes | Messages are processes only once |
No | Yes | Destination is known |
Yes | No | Consumer needs to be active |
No | Yes | Consumer Acknowledgement |
Bridge | Route | |
On the same server | On different server | Route messages to a queue |
Yes | No | Possible to have different type of source and destination (For instance: queue to topic) |
No | Yes (Topic only) | Can be transitive (a->b->c means a->c) |
Yes | Yes (Topic only) | Filters via selectors |
Yes | No | Restart JMS server when config changes |
- | Single-Hop | Hops allowed |
bridges.conf | routes.conf | Config file |
Good work! I'm glad I found your article. Keep us posted.
ReplyDeleteTIBCO BW Online Training Course
TIBCO BW 6.X Online Training
TIBCO BW 6.x training in Ameerpet
TIBCO BW 6.x training in Hyderabad