Producers

Choose the programming language or framework for your producer

There are many ways you can produce data to your stream. We support the following ways to both produce and consume data.

Use the options below to follow the right steps for your client type.

java producer
NET producer
python producer
REST producer

Java Producer Application using the Java Client

.NET Producer Application using the .NET Client

Python Producer Application using the Python Client

REST Producer using any tool that can perform REST calls

Choose the Authentication Method

Producing using SASL

In order to create a producer application that use SASL, you need to use Kafka Client.

SASL support has not been implemented for Axual Client, so if you want to implement your example based on SASL, please use Kafka Client.

Producing using Mutual TLS

In order to create a producer application that use mTLS, you can choose from following clients:

When to Choose Which Client?

Client Type

When to Choose

Supported Authentication Method

Kafka Client

Use Kafka client when you don’t need a switching logic and want to produce/consume to/from single cluster.

NOTE: When using kafka client, you need to provide the fully resolved stream name & group.id to the configuration.

SASL

Mutual TLS

Axual Client

Use Axual client when you are using the multi-cluster feature, and you want the client switching logic and client doing all the stream name & group.id resolving internally while producing/consuming data.

Mutual TLS

Spring Client

Use Spring client when you want to use Java as programming language with Spring framework (Spring-Boot) combined with Axual client.

Mutual TLS

REST Client

Use REST client when you cannot use the native Axual Client and need to use low volume streams. It provides basic produce, consume and Avro schema resolve capabilities.

Mutual TLS