No more typing reviews! Try our Samantha, our new voice AI agent.

Apache Kafka on Confluent Cloud vs Mirth Connect Health Check comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Apache Kafka on Confluent C...
Average Rating
8.6
Reviews Sentiment
5.6
Number of Reviews
14
Ranking in other categories
Streaming Analytics (16th)
Mirth Connect Health Check
Average Rating
7.8
Number of Reviews
5
Ranking in other categories
AWS Marketplace (28th)
 

Mindshare comparison

Apache Kafka on Confluent Cloud and Mirth Connect Health Check aren’t in the same category and serve different purposes. Apache Kafka on Confluent Cloud is designed for Streaming Analytics and holds a mindshare of 1.2%, up 0.5% compared to last year.
Mirth Connect Health Check, on the other hand, focuses on AWS Marketplace, holds 0.2% mindshare, up 0.2% since last year.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Kafka on Confluent Cloud1.2%
Databricks7.4%
Apache Flink6.9%
Other84.5%
Streaming Analytics
AWS Marketplace Mindshare Distribution
ProductMindshare (%)
Mirth Connect Health Check0.2%
Finimize Daily News API0.3%
Genesis VNA0.3%
Other99.2%
AWS Marketplace
 

Featured Reviews

AF
Lead Software Engineer at a tech vendor with 10,001+ employees
Has unified log streams from multiple systems and accelerated issue tracking through streamlined setup
I think Apache Kafka on Confluent Cloud can be improved by probably working more around Confluent or the tool. In my opinion, it should utilize the response structures in a better way or be able to detect if there is any variable or if there is any data structure that is mismatched, as it would be easier than us manually having to put in the exact name in order for it to match the response. Regarding additional improvements, I would say probably around error handling, where when we encounter errors specific to our response structures and everything, or the tables or anything of that nature, it would be better if we were prompted with better error handling mechanisms. I do not think there are any other improvements Apache Kafka on Confluent Cloud needs, aside from error handling and response structures.
reviewer2902977 - PeerSpot reviewer
Senior Software Engineer at a manufacturing company with 10,001+ employees
Streamlines clinical data exchange and has improved HL7 to FHIR transformation and monitoring
The best features Mirth Connect Health Check offers are that it provides a graphical way to create channels, source connectors, destination connectors, filters, and transformers without the need for extensive coding. The dashboard messages browser allows me to track message status, receiving, send, error, and troubleshooting issues quickly. It supports HL7, XML, JSON, and TCP/IP and HTTPS, RESTful APIs, and databases. Out of all those features, I find myself appreciating the troubleshooting issues, error identification, the API, and multiple protocols the most. The message browser logs, test messages, and connection testing make troubleshooting easier than many custom integration solutions. It also provides JavaScript and custom libraries that can be integrated for advanced use cases. In our organization, we are mostly using patient care devices, services, and order APIs. So mostly, EMR data, we are integrating with Mirth Connect Health Check as an HL7 integration. For the outbound, we are sending using RabbitMQ to device applications. Since using Mirth Connect Health Check, I have noticed that it has definitely reduced a lot of time as an HL7 or healthcare data integration. Different data formats require compliance and other aspects, but if I go with some other native language, it takes more time to build an application. Mirth Connect Health Check is very easy to use.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The benefits that I have seen from having a real-time architecture include better velocity for developers; instead of developing many of those capabilities in each team, we can rely on Apache Kafka on Confluent Cloud to provide those functionalities we want, and the teams can focus on their own business instead of providing all sorts of APIs and dependencies to other domains, allowing everyone to run faster."
"Some of the best features with Apache Kafka on Confluent Cloud are streaming and event capabilities, which are important due to scalability and resiliency."
"It's very fast and helps us to create the project, guarantee the message delivery, and the performance."
"Confluent Cloud handles data volume pretty well."
"Confluent helped me to streamline all those logs into one place, and then I was consuming those logs that were produced, which made it very much easier because I know Kafka and using Confluent made it much simpler."
"The state-saving feature is very much appreciated. It allows me to rewind a certain process if I see an error and then reprocess it."
"In case of huge transactions on the web or mobile apps, it helps you capture real-time data and analyze it."
"Kafka provides handy properties that allow us to directly configure the data, whether to keep it or discard it after use."
"Since using Mirth Connect Health Check, I have noticed that it has definitely reduced a lot of time as an HL7 or healthcare data integration."
"Mirth Connect Health Check has positively impacted my organization by speeding up deployment time in my previous jobs."
"Mirth Connect Health Check has positively impacted my organization by making integration seamless and being developer-friendly."
"Mirth Connect Health Check has positively impacted my organization by allowing our interoperability master, who knows how the message should be drafted and sent but is not a technical person, to use this tool easily."
"Having all the data in a single application helped my team by saving time and improving accuracy."
 

Cons

"I thought Confluent would stop me when I crossed the credits, but it did not, and then I got charged."
"There are some premium connectors, for example, available in Confluent, which you cannot access in the marketplace, so there are some limitations."
"In terms of improvements, observability and monitoring are areas that could be enhanced. They are lacking in terms of observability and monitoring compared to other products."
"Although, specifically with Apache Kafka on Confluent Cloud, it was a bit more challenging to increase adoption because it's very expensive."
"Some areas for improvement in Apache Kafka on Confluent Cloud include issues faced during migration with Kubernetes pods."
"The solution is expensive."
"There's one thing that's a common use case, but I don't know why it's not covered in Kafka. When a message comes in, and another message with the same key arrives, the first version should be deleted automatically."
"Improvement can be made by making it easier to build applications on the real-time stream, focusing on real-time pre-processing and anomaly detection."
"One main challenge I faced was because I was using a 32-bit application, and the amount of data that we were collecting was significant since it was our country's biggest laboratory, processing thousands of samples every day."
"Mirth Connect Health Check can be improved mainly in the JavaScript coding section, where it does not give me good access to the variables and the inside of class codes so that I can customize things on my own, which depends on the behavior of Mirth using the reference of their open-source Java code."
"Mirth Connect Health Check's scalability is pretty good for small to medium hospitals, but for bigger installations, we had issues talking about millions of messages per day, and that's why we ended up coding our own solution."
"The weakness part is that the UI is somewhat outdated, making it difficult to manage with large environments, and it requires JavaScript knowledge for advanced development."
"I believe Mirth Connect Health Check could be improved as the interface should be slightly better."
 

Pricing and Cost Advice

"Regarding pricing, Apache Kafka on Confluent Cloud is not a cheap tool. The right use case would justify the cost. It might make sense if you have a high volume of data that you can leverage to generate value for the business. But if you don't have those requirements, there are likely cheaper solutions you could use instead."
"I think the pricing is fair, but Confluent requires a little bit more thinking because the price can go up really quickly when it comes to premium connectors."
"I consider that the product's price falls under the middle range category."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
15%
Financial Services Firm
12%
Manufacturing Company
9%
Comms Service Provider
9%
Construction Company
37%
Healthcare Company
11%
Comms Service Provider
11%
Outsourcing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise3
Large Enterprise8
No data available
 

Questions from the Community

What needs improvement with Apache Kafka on Confluent Cloud?
I think Apache Kafka on Confluent Cloud can be improved by probably working more around Confluent or the tool. In my opinion, it should utilize the response structures in a better way or be able to...
What is your primary use case for Apache Kafka on Confluent Cloud?
I have used Apache Kafka on Confluent Cloud for one of my projects with regard to log monitoring. My main use case for Apache Kafka on Confluent Cloud in that project was mainly streaming of the lo...
What advice do you have for others considering Apache Kafka on Confluent Cloud?
My advice to others looking into using Apache Kafka on Confluent Cloud is that it is easier and has a low learning curve. If there is any use case regarding streaming, I would suggest starting off ...
What needs improvement with Mirth Connect Health Check?
An improvement point I see for Mirth Connect Health Check is a heavier version in terms of memory. I chose eight out of ten because it is not a web application.
What is your primary use case for Mirth Connect Health Check?
My main use case for Mirth Connect Health Check is to gather data for my healthcare client. We used to gather data from the clinical instruments in Mirth Connect and then translate that data throug...
What advice do you have for others considering Mirth Connect Health Check?
I would advise others looking into using Mirth Connect Health Check to look for its capability in handling data. If that suffices your requirements, definitely go ahead, and also check for a web-ba...
 

Overview

Find out what your peers are saying about Databricks, Microsoft, Apache and others in Streaming Analytics. Updated: September 2026.
915,341 professionals have used our research since 2012.