Difference Between TIBCO EMS Queues And Topics

TIBCO EMS Queues and Topics are used for JMS messaging for Point to Point and Pub-sub communication respectively for TIBCO BW projects. In TIBCO EMS based messaging, there are two supported models.

  • Queue Based Communication
  • Topic Based Communication

 

Queue Based Communication

In case of Queue based JMS communication, point to point messaging mechanism is used. Queues are maintained on centralized EMS Server and messages flow from one publisher to one subscriber via EMS Server.

EMS Publisher–>EMS Server–> EMS Subscriber

Queues based messaging is point to pint but it should not be confused with peer to peer messaging as centralized EMS Server is responsible for storing and routing messages.

Topic Based Communication

Topic based EMS Communication is used as publish-subscribe communication model for one-to-many and many-to-many message sending. Just like Queues, topics are also maintained at a centralized EMS Server. For a particular topic, there can be any number of publishers and any number of subscribers.

Recommended Reading: TIBCO EMS Durable Subscription for Topic Messages Persistence

Should I use queues or topics?

While developing any EMS based application in TIBCO, one key decision to be taken is whether to use topics or queues? Consider following points while taking this decision:

  • If messages published on EMS Server are broadcast nature for which you want multiple subscribers to listen, topics should be preferred.
  • If you want to ensure that messages are delivered one by one to every subscriber with reliability, consider point to point communication model by using queues.

 

 

Ajmal Abbasi

Ajmal Hussain Abbasi is Integration Consultant By Profession with 13+ years experience in Integration domain mainly with TIBCO products. He has extensive practical knowledge of TIBCO Business Works, TIBCO Cloud, TIBCO Flogo, TIBCO Mashery, TIBCO Spotfire, EMS and TIBCO ActiveSpaces. He has worked on a number of highly critical integration projects in various sectors by using his skills in TIBCO Flogo, TIBCO API Management (Mashery), TCI, Tibco Designer, TIBCO Business Studio, Adapters, TIBCO EMS, RV, Administrator, TIBCO BE, TIBCO ActiveSpaces etc. Ajmal Abbasi has experience with MuleSoft ESB as well. Ajmal Abbasi is also experienced in the area of API Management particularly with WSO2 API management platforms. Ajmal Abbasi is also experienced in developing solutions using Core Java and J2EE Technologies. You can contact Ajmal Abbasi for Consultancy, Technical Assistance and Technical Discussions.

More Posts - Website - Facebook - LinkedIn - YouTube

7 thoughts on “Difference Between TIBCO EMS Queues And Topics

  1. Naveen Kumar

    Hi Ajmal,

    Your articles are really good and beneficial for the beginners of Tibco.

    I have a query here.Could you please let me know how to create dynamic topics from tibco administartor.

    Thanks in Advance.

    Regards,
    Naveen.

    Reply
  2. Mary

    Hi Ajmal,

    Thanks for your articles. I have a doubt that why queues are used even topics can do the job of queue. Any specific reason?

    Reply
      1. MaryReeta

        Can you please explain elaborately. why queues are required even topics can also used for load balancing.

        Reply
  3. Emmanuel Romulus

    Queues guarantee that the message will be delivered to its receiver. If the receiver cannot be reached, the message may be stored in a database to be resubmitted later after a certain interval until the receiver receives it.

    Topics does not provide such guarantee. It is used in fire-and-forget fashion. Whoever is listening (Subscribers) can pick up the message that was broadcast. Those messages are not stored in a database to be republished if no one picked them up.

    Reply

Leave a Reply to Naveen Kumar Cancel reply

Your email address will not be published. Required fields are marked *