cli VS kcat

Confluent CLI - https://docs.confluent.io/confluent-cli/current/overview.html

Confluent Community License

Congrats on this! I noticed though that the license [1] this is provided under puts restrictions on use and therefore wouldn't typically be considered open source, at least as per the commonly regarded open source definition, but maybe instead just "source available".

[1]: https://github.com/confluentinc/cli/blob/main/LICENSE

So, is JR yet another faking library written in Go? Yes and no. JR indeed implements most of the APIs in fakerjs and Go fake it, but it's also able to stream data directly to stdout, Kafka, Redis and more (Elastic and MongoDB coming). JR can talk directly to Confluent Schema Registry, manage json-schema and Avro schemas, easily maintain coherence and referential integrity. If you need more than what is OOTB in JR, you can also easily pipe your data streams to other cli tools like kcat thanks to its flexibility.

This deployment creates a kcat container we can use to produce and consume messages.

Now we don't see any additional output. To verify it worked, let's use kafkacat to consume the topic's events. (We install kafkacat in the Dev Container. Please run the following command in VSCode's terminal)

Before we come to an end here, let's explore one additional helpful tool: kcat (formerly known as kafkacat).

Let's look at the data in the ad_events topic from the Kafka broker and see if we can identify the problem. We'll install kcat (formerly kafkacat):

kcat (formerly KafkaCat) - https://github.com/edenhill/kcat

Start with multiple consumers and produce events (this gives a sense about consistency or need for reliable data) - Producer could be command line or kafkacat

kcat is an awesome tool to make our life easier, it allows us to read and write from kafka topics without tons of scripts and in a more user-friendly way.

kcat