Let's look at how Console handles data exploration:Ĭonduktor Console can display all of your topics and consumer groups, as well as the messages that have been consumed in just a few clicks. Conduktor Console simply offers more features and covers more use cases than anything else available. There are a number of paid and open source tools that try to simplify Kafka, but Conduktor has always been first-class. The Conduktor Console Differenceįew organizations stick with the CLI given its difficulty and poor interface. And once you get to the more complicated operations, even experts won't be able to keep up. However, the Conduktor Console will be that simple for everyone, every time, no experience needed. Perhaps it is a bit unfair - a Kafka expert could be a lot faster with the CLI we didn't use terminal history and we made a spelling mistake on purpose. Of course, this is a very simple example of what you might do with Kafka, but the difference is still vast. In this clip, we are creating a topic, producing a message with a key and a value, then consuming that message: Let's do a simple comparison shot against the CLI. Kafka is well named, for it presents an impassable bureaucracy to new users. The need for an easier way to interact with Kafka is obvious from the moment you start. If you have used Apache Kafka at any point, this question will be a bit redundant. The Console's features are divided into three main parts: Explorer, Operations, and Troubleshooting, though all three work together to contribute to simplifying Kafka.Ĭonduktor Console was built on the foundations of the original Conduktor desktop application but brings a number of new features and improvements. The next in our lineup of solution deep dives is a look at the new Conduktor Console, the successor to Conduktor's DesktopUI for Apache Kafka.

Conduktor kafka series