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
IBM Event Automation
Score 8.1 out of 10
N/A
IBM Event Automation enables businesses to accelerate their event-driven efforts. The event streams, event endpoint management and event processing capabilities help lay the foundation of an event-driven architecture for unlocking the value of events.
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.
IBM Event Streams is well suited for companies developing event driven Microservices. One of the biggest challenger with microservices is that your data gets distributed into little silos - event streaming (or better known as event sourcing) allows you to get a central source of truth in your event store. We are taking this approach with IBM Event Streams and it is well suited for building an event streaming / sourcing architecture.
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).
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
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
The product was very user friendly and extremely easy to get started with. The documentation is excellent and the free tier makes it very easy to get started with without having to make deep or long term financial commitments.
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 met with the support team and they have deep technical and development understanding of the needs and the problems which IBM Event Streams addresses. If you are looking for a product backed by a highly technical support team then IBM Event Streams is probably the best choice. I was specifically impressed by the level of technical understanding my support team demonstrated.
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.
In Event Streams, applications send data by creating a message and sending it to a topic. To receive messages, applications subscribe to a topic. High availability and reliability. Event Streams offers a highly available and reliable Apache Kafka service running on IBM Cloud. Event Streams. Event Streams stores three replicas of your data to ensure the highest level of resilience across three availability zones.
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.
In using downstreams, the minimal features and the rate of releases were slow, makes us feel that there's no upgrades and other than that there's poor marketing of the product.
The adoption around the service is low, requires focused marketing.
Lack of visibility into topic depth , Monitoring capabilities
