Apache Kafka vs. webMethods.io Integration

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Kafka
Score 8.2 out of 10
N/A
Apache Kafka is an open-source stream processing platform developed by the Apache Software Foundation written in Scala and Java. The Kafka event streaming platform is used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.N/A
webMethods.io Integration
Score 9.0 out of 10
N/A
webMethods.io Integration (formerly webMethods Integration Cloud) from Software AG is designed to make it easy to connect SaaS apps and make business processes more efficient. It enables enterprise subject matter experts and eliminates integration silos, allowing users to integrate applications hosted in public or private clouds, as well as applications hosted on premises.N/A
Pricing
Apache KafkawebMethods.io Integration
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache KafkawebMethods.io Integration
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details——
More Pricing Information
Community Pulse
Apache KafkawebMethods.io Integration
Considered Both Products
Apache Kafka

No answer on this topic

webMethods.io Integration
Chose webMethods.io Integration
webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods …
Top Pros
Top Cons
Features
Apache KafkawebMethods.io Integration
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
Apache Kafka
-
Ratings
webMethods.io Integration
7.7
1 Ratings
5% below category average
Pre-built connectors00 Ratings8.01 Ratings
Connector modification00 Ratings9.01 Ratings
Support for real-time and batch integration00 Ratings8.01 Ratings
Data quality services00 Ratings7.01 Ratings
Data security features00 Ratings7.01 Ratings
Monitoring console00 Ratings7.01 Ratings
Best Alternatives
Apache KafkawebMethods.io Integration
Small Businesses

No answers on this topic

Make
Make
Score 9.4 out of 10
Medium-sized Companies
IBM MQ
IBM MQ
Score 9.1 out of 10
IBM App Connect
IBM App Connect
Score 9.1 out of 10
Enterprises
IBM MQ
IBM MQ
Score 9.1 out of 10
IBM App Connect
IBM App Connect
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache KafkawebMethods.io Integration
Likelihood to Recommend
8.3
(18 ratings)
9.0
(1 ratings)
Likelihood to Renew
9.0
(2 ratings)
-
(0 ratings)
Usability
10.0
(1 ratings)
-
(0 ratings)
Support Rating
8.4
(4 ratings)
-
(0 ratings)
User Testimonials
Apache KafkawebMethods.io Integration
Likelihood to Recommend
Apache
Apache Kafka is well-suited for most data-streaming use cases. Amazon Kinesis and Azure EventHubs, unless you have a specific use case where using those cloud PaAS for your data lakes, once set up well, Apache Kafka will take care of everything else in the background. Azure EventHubs, is good for cross-cloud use cases, and Amazon Kinesis - I have no real-world experience. But I believe it is the same.
Read full review
Software AG
We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios.
Read full review
Pros
Apache
  • Really easy to configure. I've used other message brokers such as RabbitMQ and compared to them, Kafka's configurations are very easy to understand and tweak.
  • Very scalable: easily configured to run on multiple nodes allowing for ease of parallelism (assuming your queues/topics don't have to be consumed in the exact same order the messages were delivered)
  • Not exactly a feature, but I trust Kafka will be around for at least another decade because active development has continued to be strong and there's a lot of financial backing from Confluent and LinkedIn, and probably many other companies who are using it (which, anecdotally, is many).
Read full review
Software AG
  • Easy to use
  • Priced competitively
  • Supports robust and resilient integration solutions
Read full review
Cons
Apache
  • Sometimes it becomes difficult to monitor our Kafka deployments. We've been able to overcome it largely using AWS MSK, a managed service for Apache Kafka, but a separate monitoring dashboard would have been great.
  • Simplify the process for local deployment of Kafka and provide a user interface to get visibility into the different topics and the messages being processed.
  • Learning curve around creation of broker and topics could be simplified
Read full review
Software AG
  • Complex logic is hard to understand in simple diagrammatic user interface
  • User interface too simplistic for solutions that are complicated or go against the grain
  • Runtime observability could be improved
Read full review
Likelihood to Renew
Apache
Kafka is quickly becoming core product of the organization, indeed it is replacing older messaging systems. No better alternatives found yet
Read full review
Software AG
No answers on this topic
Usability
Apache
Apache Kafka is highly recommended to develop loosely coupled, real-time processing applications. Also, Apache Kafka provides property based configuration. Producer, Consumer and broker contain their own separate property file
Read full review
Software AG
No answers on this topic
Support Rating
Apache
Support for Apache Kafka (if willing to pay) is available from Confluent that includes the same time that created Kafka at Linkedin so they know this software in and out. Moreover, Apache Kafka is well known and best practices documents and deployment scenarios are easily available for download. For example, from eBay, Linkedin, Uber, and NYTimes.
Read full review
Software AG
No answers on this topic
Alternatives Considered
Apache
I used other messaging/queue solutions that are a lot more basic than Confluent Kafka, as well as another solution that is no longer in the market called Xively, which was bought and "buried" by Google. In comparison, these solutions offer way fewer functionalities and respond to other needs.
Read full review
Software AG
webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
Read full review
Return on Investment
Apache
  • Positive: Get a quick and reliable pub/sub model implemented - data across components flows easily.
  • Positive: it's scalable so we can develop small and scale for real-world scenarios
  • Negative: it's easy to get into a confusing situation if you are not experienced yet or something strange has happened (rare, but it does). Troubleshooting such situations can take time and effort.
Read full review
Software AG
  • webMethods.io Integration is a cost effective approach to integration in isolation
  • webMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costs
  • webMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic Apps
  • webMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used
Read full review
ScreenShots