Confluent vs. TIBCO Messaging

TIBCO Messaging

Overview
Product	Rating	Most Used By	Product Summary	Starting Price
Confluent	Score 9.9 out of 10	N/A	Confluent Cloud is a cloud-native service for Apache Kafka used to connect and process data in real time with a fully managed data streaming platform. Confluent Platform is the self-managed version.	$0
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

Confluent

TIBCO Messaging

Editions & Modules

Basic: $0
Standard: Starting at ~$385
per month
Enterprise: Starting at ~$1,150
per month

No answers on this topic

Offerings

Pricing Offerings
Confluent	TIBCO Messaging
Free Trial
No	No
Free/Freemium Version
Yes	No
Premium Consulting/Integration Services
No	No

Entry-level Setup Fee

No setup fee

Additional Details

Confluent monthly bills are based upon resource consumption, i.e., you are only charged for the resources you use when you actually use them: Stream: Kafka clusters are billed for eCKUs/CKUs ($/hour), networking ($/GB), and storage ($/GB-hour). Connect: Use of connectors is billed based on throughput ($/GB) and a task base price ($/task/hour). Process: Use of stream processing with Confluent Cloud for Apache Flink is calculated based on CFUs ($/minute). Govern: Use of Stream Governance is billed based on environment ($/hour). Confluent storage and throughput is calculated in binary gigabytes (GB), where 1 GB is 2^30 bytes. This unit of measurement is also known as a gibibyte (GiB). Please also note that all prices are stated in United States Dollars unless specifically stated otherwise. All billing computations are conducted in Coordinated Universal Time (UTC).

—

More Pricing Information

Community Pulse
	Confluent	TIBCO Messaging
Considered Both Products	Confluent Verified User Anonymous Chose Confluent For our use case it was very important that the technology we were working with fit into our Azure architecture, and met our data processing size requirements to stream data within certain SLAs. Confluent more than met our performance requirements and compared to the others … Incentivized Helpful? Verified User Anonymous Chose Confluent We chose to use the Confluent Platform because they provide enterprise-grade customer service support. Whenever we have trouble setting up or using the service, we can create a ticket for them and it will be resolved pretty fast. Kafka is the open-source software that comes … 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?

Features

Confluent

TIBCO Messaging

Streaming Analytics

Comparison of Streaming Analytics features of Product A and Product B
	Confluent 9.1 Ratings 13% above category average	TIBCO Messaging - Ratings
Real-Time Data Analysis	10.00 Ratings	00 Ratings
Visualization Dashboards	8.00 Ratings	00 Ratings
Data Ingestion from Multiple Data Sources	10.00 Ratings	00 Ratings
Low Latency	9.00 Ratings	00 Ratings
Integrated Development Tools	8.00 Ratings	00 Ratings
Linear Scale-Out	9.00 Ratings	00 Ratings
Data Enrichment	10.00 Ratings	00 Ratings

Best Alternatives
	Confluent	TIBCO Messaging
Small Businesses	IBM Streams (discontinued) Score 9.0 out of 10	No answers on this topic
Medium-sized Companies	Tealium Customer Data Hub Score 8.2 out of 10	Apache Kafka Score 7.7 out of 10
Enterprises	Spotfire Streaming Score 6.6 out of 10	Apache Kafka Score 7.7 out of 10
All Alternatives	View all alternatives	View all alternatives

User Ratings
	Confluent	TIBCO Messaging
Likelihood to Recommend	10.0 (0 ratings)	7.7 (0 ratings)
Likelihood to Renew	- (0 ratings)	8.0 (0 ratings)
Support Rating	10.0 (0 ratings)	- (0 ratings)

User Testimonials
	Confluent	TIBCO Messaging
Likelihood to Recommend	If your company needs to build event-driven applications, like in healthcare industry, you need to enhance interoperability, and you are seeking a reliable service with enterprise-grade support, Confluent is the best on the market you can get. Their product works great and they provide very good customer service. 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	Products work great. Training is available. Customer support is good. 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	Cloud based Azure platform features for Confluent lacks behind AWS And GCP Incentivized Verified User Anonymous 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
Support Rating	The support from the Confluent platform is great and satisfying. We have been working with Confluent for more than a year now. They sent out resident architects to help us set up Confluent cluster on our cloud and help us troubleshoot problems we have encountered. Overall, it has been a great experience working with the Confluent Platform. Incentivized Verified User Anonymous Read full review	No answers on this topic
Alternatives Considered	For our use case it was very important that the technology we were working with fit into our Azure architecture, and met our data processing size requirements to stream data within certain SLAs. Confluent more than met our performance requirements and compared to the others scale options and cost to run it was more than financially viable as a platform solution to our global operations. Incentivized Verified User Anonymous 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	Confluent replaced Microsoft Event Hubs in our environment and unblocked data platform services rollout globally. 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