Apache Camel vs. TIBCO Messaging

Apache Camel

Apache Camel

34 Reviews and Ratings

TIBCO Messaging

TIBCO Messaging

78 Reviews and Ratings

Overview
Product	Rating	Most Used By	Product Summary	Starting Price
Apache Camel	Score 6.3 out of 10	N/A	Apache Camel is an open source integration platform.	N/A
TIBCO Messaging	Score 7.7 out of 10	N/A	TIBCO offers high-performance messaging technology, and gives customers flexibility and unique choice between Commercial and Open-source messaging solutions. TIBCO Messaging is a comprehensive messaging portfolio available to meet a wide variety of use cases and deployment models.	N/A

Pricing

Apache Camel

TIBCO Messaging

Editions & Modules

No answers on this topic

No answers on this topic

Offerings

Pricing Offerings
Apache Camel	TIBCO Messaging
Free Trial
No	No
Free/Freemium Version
No	No
Premium Consulting/Integration Services
No	No

Entry-level Setup Fee

No setup fee

No setup fee

Additional Details

—

—

More Pricing Information

Community Pulse
	Apache Camel	TIBCO Messaging
Considered Both Products	Apache Camel Verified User Anonymous Chose Apache Camel Easier to use, better routing system, but perhaps too basic dependant on business needs? Incentivized Helpful? Verified User Anonymous Chose Apache Camel 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 … Incentivized Helpful? Verified User Anonymous Chose Apache Camel working with Apache's TomCat server, our developer found it most easy given the UI of Camel to perform integration and data processing tasks. when compared to the other two softwares they felt the need to learn new tools outside of Apache family can be avoided and with kafka, … Incentivized Helpful? Verified User Anonymous Chose Apache Camel WebSphere Message Broker - Expensive, old, hard to use, bad connectors Mulesoft - Very similar to Camel, but expensive and buggy Incentivized Helpful? Verified User Anonymous Chose Apache Camel We did a comparison of the two products with an example application that tested about 10 distinct EIP pattern. We wrote Camel in XML and Java DSL and SI in XML. This was about 3 years ago. At the time, I found the threading model in SI to be more intuitive and Camel's seda. … Incentivized Helpful? Verified User Anonymous Chose Apache Camel Akka or Spring Integration/ XD are alternatives to Apache Camel and very good frameworks on their own (especially Akka which provides a single threaded illusion). Incentivized Helpful? Akmal Muqeeth Lead Software Engineer Chose Apache Camel We chose Apache Camel because it was lightweight, easy to get started with and because it had a groovy DSL since we were a grails shop when we started using it. Incentivized Helpful? SS Surjit Sen Senior Software Consultant at Randstad Chose Apache Camel Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox. Incentivized Helpful? David McCann Senior Software Engineer Chose Apache Camel Esper is only similar in that they both are involved in complex even processing, however Esper's aim is a little more complex and specialized. In general however I found Apache Camel to be much easier to understand, implement and debug, whereas Esper's DSL can get very … Incentivized Helpful? Verified User Anonymous Chose Apache Camel Jax-rs Incentivized Helpful?	TIBCO Messaging Verified User Anonymous Chose TIBCO Messaging Admin Tools for Jira Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging TIBCO is an alternate method but does not meet all the needs of cloud -native system. Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging We chose TIBCO Messaging not just for its performance but because it looked like the natural way to pave our existing TIBCO Integration architecture. Setting up TIBCO EMS servers and objects seems more straightforward than with most of competitors. It is easy to configure and … Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging We also use other messaging products: IBM MQ, especially for integration with other systems (server2server), which has been an industry standard for a long time, and Apache Kafka for cloud-native applications. EMS is a worse option compared to them, but it is still acceptable. Incentivized Helpful? OH Olivier HASCOET Program Manager Chose TIBCO Messaging No real hesitation has this product was natively compatible to make a proper communication between the two TIBCO products we USE (TIBCO Business Works and TIBCO Active Matrix BPM). Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging MQ was way more expensive and it is limited in many ways against TIBCO Enterprise Message Service. MQ does not allow easy topic to queue bridging and also requires much more configuration for basic types of activities. Does not support all of the same JMS headers that TIBCO … Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging We have both products installed. We prefer on product over the other based on applications requirements. We have no preferences on these products, we are using both with good results! Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging TIBCO is not the industry leader in general but for our unique case and also because we also deployed TIBCO MFT Platform Server, it was the go to choice. The recent improvements like container support also gave us confidence that this is a product for the future. Moving from an … Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging TIBCO Enterprise Message Service serves as a "barebone" service in our environment. Some applications use TIBCO Rendezvous, others EMS. This allowed us to evaluate the differences and I saw that EMS is more robust and open to different programming languages. In particular, the … Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging IBM MQ was the old product we used, and we migrated from it to TIBCO EMS. We use also RabbitMQ for our light-weight IPC scenarios and Kafka for our data stream use cases. They 3 compose our complete messaging and streaming solution. Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging Rabbit is much easier to use and get started with thanks to its online, free, public tutorials and availability of the software on public repositories like Dockerhub, Maven Central, NuGet, etc. Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging At the time we made the selection and purchase, we found it to be a performant technology. Also, TIBCO was a young company at that time. In order to have us as ther first major client, they accepted to give us a huge discount on their products, including EMS (that's the main … Incentivized Helpful? SK Sharath Kandera Integration Manager Chose TIBCO Messaging IBM MQ series is a messaging product . You will need to use IBM product suit heavily and it works better but personaly I have not used it. Apache MQ is also a messaging bus and I have come across it with SAP . EMS is light weigh as its written in C language and easy to implement. Incentivized Helpful? Luca de Falco Tibco Consultant Chose TIBCO Messaging Integration with Tibco BusinessWorks is out of the box. JMS and JNDI configuration is very easy using the available wizard. Client configuration is very simple. Capability to validate the connection at design time. Incentivized Helpful? HR Hugo Romani Cortes Atos - Middleware Architect Chose TIBCO Messaging TIBCO Enterprise Message Service was selected because of the contract with TIBCO. We generally see company buying other TIBCO products such as TIBCO BusinessWorks and then TIBCO offers some discount on their "minor" products. If I would compare technical capabilities of EMS … Incentivized Helpful? Ankit Gupta IT Analyst Chose TIBCO Messaging It is easy to configure, develop, upgrade and maintain using TIBCO Emterprise Message Service compared to other products on the market. Deployment or setup of new environments can be automated. Support from theTIBCO engineering team is very responsive and effective. Incentivized Helpful? Salah BENAMIRA Consultant ESB \| API Management Chose TIBCO Messaging We selected TIBCO EMS because we selected TIBCO BW as an ESB. TIBCO EMS must be installed in the TIBCO BW stack. I prefer TIBCO EMS because it implements very powerful functionality like bridges and routing. Incentivized Helpful? JY Joe Yee IT Strategic Technical Advisor Chose TIBCO Messaging Tibco EMS was among the top choices after extensive research by our internal R&D team. It was select for performance, scalability, and supportability. Incentivized Helpful? Arnaud Giffard Solution Architect Chose TIBCO Messaging TIBCO Enterprise Message Service has been chosen by the customer because it had many contracts with TIBCO products and it has been full integrated with a TIBCO BusinessWorks platform. Moreover, TIBCO Enterprise Message Service has all required functionalities searched for the … Incentivized Helpful? NK Nagasujith K Tech Manager Chose TIBCO Messaging I have worked only on TIBCO EMS. Incentivized Helpful? Verified User Anonymous Chose TIBCO Messaging Tibco RendezVous is the underlying technology that makes messaging exchange super fast. Incentivized Helpful? Juan Francisco Tavira Global Technology Centre - Middleware Chose TIBCO Messaging Better integration with BW, easier to setup and a very good support whereas others lack some of them. Kafka is a threat anyway Incentivized Helpful?

Best Alternatives
	Apache Camel	TIBCO Messaging
Small Businesses	No answers on this topic	No answers on this topic
Medium-sized Companies	Boomi Score 8.9 out of 10	Apache Kafka Score 7.7 out of 10
Enterprises	TIBCO B2B Integration Solution Score 8.0 out of 10	Apache Kafka Score 7.7 out of 10
All Alternatives	View all alternatives	View all alternatives

User Ratings
	Apache Camel	TIBCO Messaging
Likelihood to Recommend	7.9 (0 ratings)	7.7 (0 ratings)
Likelihood to Renew	- (0 ratings)	8.0 (0 ratings)

User Testimonials
	Apache Camel	TIBCO Messaging
Likelihood to Recommend	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. Incentivized Verified User Anonymous Read full review	Organization which uses TIBCO Business Works or TIBCO Business Process Management or TIBCO BPM Enterprise can make use of TIBCO Messaging as it works well with other TIBCO tools. Many TIBCO tools have TIBCO Messaging products bundled as a package along with other TIBCO tools. Use of dynamic topics and queues makes run time processing easier. Incentivized Verified User Anonymous Read full review
Pros	open source and a great set of component feature set - always latest features available for integration works well with spring boot great community and support for any kind of workflow based on enterprise integration patterns which helps our developers achieve integration tasks with all kinds of API services Incentivized Verified User Anonymous Read full review	Tibco EMS performs very well, and it meets our stringent performance requirements for corporate messaging backbone. Tibco EMS scales well, and this is another of our stringent requirements. Tibco provides good support for the EMS product, and continues to improve it. This is important as we don't want to use something that does not keep up with the changes in the technology landscape. Incentivized JY Joe Yee IT Strategic Technical Advisor Read full review
Cons	Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention. Incentivized David McCann Senior Software Engineer Read full review	A bit of lag time between data sync and the data reaching the server for some of our field sites. It still seems like a niche product for me with little community support. I didn't know about it before working for a company that deployed it. Certain functionality is too complex to setup as compared to other products on the market. Incentivized Verified User Anonymous Read full review
Likelihood to Renew	No answers on this topic	EMS is a solid system and I see no reason to abandon it, in fact I am eager to see what the next versions will offer and future road maps. Knowing we have support to help us in case of problems is invaluable, both in case of critical issues and to improve overall performance. Incentivized Verified User Anonymous Read full review
Alternatives Considered	Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox. Incentivized SS Surjit Sen Senior Software Consultant at Randstad Read full review	We chose TIBCO Messaging not just for its performance but because it looked like the natural way to pave our existing TIBCO Integration architecture. Setting up TIBCO EMS servers and objects seems more straightforward than with most of competitors. It is easy to configure and easy to use and understand. Incentivized Verified User Anonymous Read full review
Return on Investment	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. Incentivized Verified User Anonymous Read full review	Improved developer productivity as TIBCO Enterprise Message Service requires minimal coding Quicker time to market as the configuration / onboarding can be automated with this tool Ability to onboard more clients/consumers as the tool can handle large volumes seamless Improved visibility on the end to end process as the product provides monitoring by using JMS header information Verified User Anonymous Read full review
ScreenShots