Apache Kafka vs. SAP NetWeaver BPM

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.

It is well suited when we need to integrate business processes with SAP ERP and SAP CRM - the solution can be integrated with business rules/procedures defined in SAP ERP/CRM and NetWeaver can be used to monitor the rules and flag off exceptions. When there are multiple workflows running, it tends to slow down running of these processes. Also, it entirely depends on SAP portal for it to run efficiently.

Incentivized

• 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).

Incentivized

• Virtual paper trail. Iterations of process and current documentation are all stored as "artifacts", leaving a great trail.
• Configuration of users. BPM somewhat magically determines which users will be impacted and automates rules.
• A pro (that is also a con) is the design interface. If you know what you are doing, it is incredibly powerful and malleable.

• 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

• Live readings would be nice.
• Easier to maneuver
• Work with all systems with the press of one keystroke

Incentivized

Kafka is quickly becoming core product of the organization, indeed it is replacing older messaging systems. No better alternatives found yet

Incentivized

As a big fan of SAP in general, the BPM solution fits right in with all the other things SAP does well, and does it with incredible efficiency

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

Incentivized

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.

Incentivized

We have our own tech support for systems, I would say they probably could use more training on it, I don't really think it's anything regarding the SAP system, but more the knowledge they have on the system itself. It seems to take longer for them to fix any issues we may come across.

Incentivized

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.

Incentivized

I found the initial setup of NetWeaver is much simpler than other products especially in an SAP environment where we have SAP ERP/HRM/CRM as it can be well integrated with other SAP products. The only drawback is the need/dependency on SAP Portal. It is better suited in an environment where SAP ERP is running.

Incentivized

• 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.

Incentivized

• Helped us harness integrated benefit from having SAP ERP/CRM by leveraging NetWeaver to define business processes/rules and monitor exceptions
• Did not have any negative experience except for the fact that at times when multiple rules run, it can be somewhat slow

Incentivized