TIBCO EMS (Enterprise Messaging Service) is a standardized messaging platform for communication between applications and processes in enterprise environments for real time, guaranteed communication and message transfers. TIBCO EMS is based on JMS (Java Messaging Service) specification and you can call it a customization of JMS By Tibco.
TIBCO EMS is considered as an alternative to RV (Rendezvous) for application to application and server to server communication. There are certain pros and cons of TIBCO EMS that one should know before opting it as messaging platform in any integration environment.
Pros of TIBCO EMS
- Easier Application Integration
TIBCO EMS helps in faster and efficient integration of applications in an enterprise environment. With a centralized EMS server, integration becomes quite easier and simplified compared to other messaging options like RV.
- Greater Reliability In Message Delivery
TIBCO EMS based communication is considered very reliable with a guaranteed delivery of every message. EMS based messaging is preferred and recommended choice for applications with critical data.
- Secure Messaging Between Applications and Systems
TIBCO EMS provides great level of Security and administrative controls, including SSL for client-to-server and server-to-server connectivity, provide secure, message delivery, as well as plug-ins for custom-built authentication.
Cons of TIBCO EMS
- Single Point Of Failure
A single EMS server maintains all topics and queues of messages to which all applications connect to send and receive messages. This results in a single point of failure as the whole messaging environment gets dependent on availability of EMS server. On the other hand, Tibco RV works on Bus model where every node connected to bus has RVD (RV Daemon) running so no single point of failure.
- Slower Communication, Low Throughput
Compared to RV, TIBCO EMS based communication is considered slower for message communication between applications due to additional overheads associated with its reliability and message delivery guarantees.
what is recomended.. dynamic queue or statics?
thank you.