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
SAP Integration Suite
Score 8.6 out of 10
N/A
SAP Integration Suite is an integration platform-as-a-service (iPaaS) that helps quickly integrate on-premises and cloud-based processes, services, applications, events, and data. It is used to accelerate innovation, automate more processes, and realize a faster time to value.
$11,199
per year
Pricing
Apache Kafka
SAP Integration Suite
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Kafka
SAP Integration Suite
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Access to free tier services does not expire while there is an active Pay-As-You-Go or CPEA account with SAP. Once a free tier service limit has been reached users have the option to update from a free to a paid service plan in the same account.
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.
SAP Integration Suite has been helpful to our organization in eliminating manual processes but also to create custom processes that align with business requirements. It has allowed multiple vendors to integration with our SAP products and be housed in one place. The tool requires advanced technical knowledge and/or strong AMS support. I would recommend to ensure you have proper resources aligned prior to implementation.
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).
Broad Connectivity: SAP Integration Suite excels in connecting diverse systems, including SAP and non-SAP applications, databases, and third-party services.
Pre-built Integrations and Templates:The suite provides a library of pre-built integrations and templates for common business scenarios.
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
SAP Integration Suite is very helpful to us in many ways to manage purchase procedures, stocks, and data of vendors and suppliers. Also, it helps to manage data for service providers. SAP Integration Suite has the tool to conduct training and evaluation. Unique features like the cloud can provide access from any place and by any device is very helpful.
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
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.
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.
I selected it because its now one of the best thing to do and to work. As we are currently working from home it makes the work easy and comfortable and yet the main usage will be in office the environment created will be simple. The UI logic is based on some calculations which will rely on some natural intuations of mind and when it comes to mind it is easy.
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.
