Nachrichten an Kafka senden
Erkunden Sie, wie Sie Anwendungen entwickeln, die Daten effizient und zuverlässig an Kafka-Topics senden.
Nachrichten an Kafka senden ist eine kostenlose Apache Kafka & Stream Processing Fundamentals-Lektion auf CoddyKit. Dies ist Lektion 1 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Apache Kafka & Stream Processing Fundamentals-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Apache Kafka & Stream Processing Fundamentals-Kurs umfasst insgesamt 4 Lektionen.
Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.
Meet the Kafka Producer
In this lesson, we'll learn how to send messages (also called records) to Kafka topics. This is the job of a Kafka Producer.
Think of a producer as an application or service that generates data. It then sends this data to a Kafka cluster, where it's stored in specific topics for other applications to read.
- Producers generate data.
- Topics organize data streams.
- Brokers store the data.
Producer Client Basics
To send data, your application uses a Kafka Producer client library. This library handles all the complex interactions with the Kafka brokers.
It takes care of:
- Finding the right Kafka broker.
- Serializing your data into bytes.
- Retrying failed send operations.
- Balancing message distribution.
We'll use Java examples, but the concepts apply across languages.
Essential Producer Config
Before a producer can send messages, it needs some basic configuration. The two most important settings are:
bootstrap.servers: A comma-separated list of host/port pairs for Kafka brokers. The producer uses these to discover the full cluster.key.serializerandvalue.serializer: Classes that convert your message's key and value objects into byte arrays, which is how Kafka stores data.
Without these, the producer won't know where to send messages or how to format them.
Producer Config Example
Here's how you might set up these properties in Java:
import java.util.Properties;
public class ProducerConfigDemo {
public static void main(String[] args) {
Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("key.serializer", "org.apache.kafka.common.serialization.StringSerializer");
props.put("value.serializer", "org.apache.kafka.common.serialization.StringSerializer");
System.out.println("Producer properties configured!");
// In a real app, you'd create a KafkaProducer with these props
}
}Crafting Your Message: ProducerRecord
When you send data to Kafka, you don't just send a string. You send a ProducerRecord. This object encapsulates your message and its metadata.
A ProducerRecord requires:
- The topic name where the message will be sent.
- An optional key: Used for partitioning messages. Messages with the same key go to the same partition.
- The value: The actual data you want to send.
Keys are important for ensuring ordering for related data within a topic.
Sending Messages (Blocking)
The simplest way to send a message is using the send() method. If you want to wait for the message to be acknowledged by Kafka, you can call .get() on the returned Future object.
This makes the send operation synchronous (blocking). It's easy to understand, but can be slow if you're sending many messages.
import org.apache.kafka.clients.producer.*;
import java.util.Properties;
public class SyncProducer {
public static void main(String[] args) throws Exception {
Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("key.serializer", "org.apache.kafka.common.serialization.StringSerializer");
props.put("value.serializer", "org.apache.kafka.common.serialization.StringSerializer");
try (KafkaProducer<String, String> producer = new KafkaProducer<>(props)) {
ProducerRecord<String, String> record = new ProducerRecord<>(
"my-topic", "key1", "Hello Sync Kafka!");
RecordMetadata metadata = producer.send(record).get(); // Blocks here
System.out.println("Sent message: " + metadata.topic() + "-" + metadata.partition());
}
}
}Sending Messages (Non-Blocking)
For better performance, Kafka producers are designed to send messages asynchronously. When you call send(), it adds the message to a buffer and returns immediately.
The actual sending happens in the background. This allows your application to continue processing without waiting for each message to be delivered.
import org.apache.kafka.clients.producer.*;
import java.util.Properties;
public class AsyncProducer {
public static void main(String[] args) {
Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("key.serializer", "org.apache.kafka.common.serialization.StringSerializer");
props.put("value.serializer", "org.apache.kafka.common.serialization.StringSerializer");
try (KafkaProducer<String, String> producer = new KafkaProducer<>(props)) {
ProducerRecord<String, String> record = new ProducerRecord<>(
"my-topic", "key2", "Hello Async Kafka!");
producer.send(record); // Returns immediately
System.out.println("Message queued for sending.");
// In a real app, you'd send many messages here
}
}
}Handling Send Results with Callbacks
Since send() is asynchronous, how do you know if a message was successfully sent or if an error occurred? You use a Callback.
The callback function is executed once Kafka acknowledges the message or if an error prevents it from being sent. This is crucial for error handling and logging.
import org.apache.kafka.clients.producer.*;
import java.util.Properties;
public class CallbackProducer {
public static void main(String[] args) {
Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("key.serializer", "org.apache.kafka.common.serialization.StringSerializer");
props.put("value.serializer", "org.apache.kafka.common.serialization.StringSerializer");
try (KafkaProducer<String, String> producer = new KafkaProducer<>(props)) {
ProducerRecord<String, String> record = new ProducerRecord<>(
"my-topic", "key3", "Hello Callback Kafka!");
producer.send(record, new Callback() {
@Override
public void onCompletion(RecordMetadata metadata, Exception exception) {
if (exception == null) {
System.out.println("Message sent successfully to topic " + metadata.topic());
} else {
System.err.println("Error sending message: " + exception.getMessage());
}
}
});
// Must flush or close producer to ensure callback is triggered in short programs
producer.flush();
}
}
}Ensuring Delivery: Acks Configuration
Producer reliability is controlled by the acks configuration. This setting determines how many acknowledgments a producer needs from Kafka brokers before considering a message 'sent'.
acks=0: Producer sends and doesn't wait for any acknowledgment. Fastest, but lowest durability (messages might be lost).acks=1: Producer waits for the leader broker to acknowledge receipt. Good balance of speed and durability.acks=all(or-1): Producer waits for all in-sync replicas to acknowledge. Slowest, but highest durability (messages are very unlikely to be lost).
Producer Best Practices
To ensure your Kafka producers are efficient and robust:
- Always close the producer: Call
producer.close()when your application shuts down. This flushes any buffered messages and releases resources. - Batching: Kafka producers automatically batch messages for efficiency. You can tune
linger.msandbatch.sizefor optimal throughput. - Error Handling: Implement robust error handling in your callbacks to deal with transient network issues or permanent errors.
Proper configuration and resource management are key to a healthy Kafka application.
Quick Check: Producers
Which producer configuration property specifies how many acknowledgments the producer needs from Kafka brokers before considering a message successfully sent?
Producer Summary
You've learned the fundamentals of producing messages to Kafka!
- Producers send data to topics.
- Key configurations include
bootstrap.serversand serializers. - Messages are wrapped in
ProducerRecordobjects. - You can send messages synchronously (blocking) or asynchronously (non-blocking).
- Callbacks are used to handle asynchronous send results.
- The
ackssetting controls message durability.
Next, we'll dive into how applications read these messages using Kafka Consumers!
Häufig gestellte Fragen
Ist die Lektion „Nachrichten an Kafka senden“ kostenlos?
Ja — der vollständige Text von „Nachrichten an Kafka senden“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Apache Kafka & Stream Processing Fundamentals-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Apache Kafka & Stream Processing Fundamentals-Kurs umfasst insgesamt 4 Lektionen.
Was lerne ich in „Nachrichten an Kafka senden“?
Erkunden Sie, wie Sie Anwendungen entwickeln, die Daten effizient und zuverlässig an Kafka-Topics senden. Du übst Apache Kafka & Stream Processing Fundamentals mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.
Brauche ich Erfahrung, um Apache Kafka & Stream Processing Fundamentals zu starten?
Keine Vorkenntnisse erforderlich. Apache Kafka & Stream Processing Fundamentals auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 1 von 4.
Wie lange dauert die Lektion „Nachrichten an Kafka senden“?
Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.
Kann ich in dieser Apache Kafka & Stream Processing Fundamentals-Lektion Code schreiben und ausführen?
Ja. Jede Apache Kafka & Stream Processing Fundamentals-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.
Alle Lektionen in diesem Kurs
- Nachrichten an Kafka senden
- Nachrichten aus Kafka konsumieren
- Partitionen und Offsets verstehen
- Nachrichtenschlüssel und Partitionierungsstrategien