Apache Camel is an open source integration platform.
N/A
Mule ESB
Score 9.0 out of 10
N/A
Mule ESB, from Mulesoft, is an open source middleware solution.
N/A
TIBCO Rendezvous
Score 6.0 out of 10
N/A
TIBCO's Rendezvous is message oriented middleware. The software uses messages to enable distributed application programs to communicate across a wide variety of hardware platforms and programming languages.
Messaging is a very old concept offered by many software vendors, Although Tibco Rendezvous is very well recognized non-open source solution.In my opinion Tibco JMS is mostly used in all the applications than the IBM MQ and mule software -
Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages. One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.
If you’re bringing anything into Salesforce you should just invest now into Mule, you will get your money’s worth and find a myriad of uses to build APIs between many other systems. Once you build a component you can easily reuse it as a building block to attach to another source/destination. This makes it easy to ramp up quickly and spread usage of Mule throughout your enterprise. A good value for medium to large companies, but probably cheaper to outsource your job to a consulting firm if you are smaller.
TIBCO Rendezvous is a fast and reliable mode of communication, although they are already outdated by TIBCO FTL, which is even more faster and reliable than it's predecessor. They are more suitable for communication between the TIBCO products as all the TIBCO suite of products support the TIBCO Rendezvous. They are more widely used by banks and stock ticker applications to broadcast the ticker information. Most of the applications support Java JMS mode easily and out of the box than the TIBCO Rendezvous. Hence the TIBCO software themselves have their own version of the JMS server called Tibco EMS ( Tibco Enterprise messaging service).
Camel has an easy learning curve. It is fairly well documented and there are about 5-6 books on Camel.
There is a large user group and blogs devoted to all things Camel and the developers of Camel provide quick answers and have also been very quick to patch Camel, when bugs are reported.
Camel integrates well with well known frameworks like Spring, and other middleware products like Apache Karaf and Servicemix.
There are over 150 components for the Camel framework that help integrate with diverse software platforms.
It is best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.
Attending an official TIBCO classroom training, where you can have an active participation with an expert teacher, you can find the answers to all yours needs. In any case, if you are not satisfied on your requests, the teacher takes the time to find the best solution.
I had the opportunity to attend one and I could learn all features I needed for my business: now I can say TIBCO Rendezvous is very usable.
I never needed support for TIBCO Rendezvous. I always used it without any issue and until now I don't remember some situations where it interrupted its 24/7 uptime.
If you are looking for a Java-based open source low cost equivalent to webMethods or Azure Logic Apps, Apache Camel is an excellent choice as it is mature and widely deployed, and included in many vendored Java application servers too such as Redhat JBoss EAP. Apache Camel is lacking on the GUI tooling side compared to commercial products such as webMethods or Azure Logic Apps.
Very fast time to market in that so many components are available to use immediately.
Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs.
However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch).
Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge.
All a non-TIBCO based applications need to use the TIBCO Rendezvous APIs and reprogrammed to communicate with other application using the Tibco Rendezvous.
All applications and enterprises need to have an enterprise license to communicate with each other.
TIBCO offers their Rendezvous APIs in various programming languages. Hence any application can use these APIs to start using the Tibco Rendezvous. Although most application prefers not to as TIBCO Rendezvous is TIBCO 's closely guarded recipe.
