Configurare Kafka in locale con Docker
Impari a configurare rapidamente un cluster Kafka locale usando Docker Compose, creando un ambiente isolato per sviluppo e test.
Configurare Kafka in locale con Docker è una lezione Advanced Spring Boot 4: Event-Driven Architecture (Kafka) gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Advanced Spring Boot 4: Event-Driven Architecture (Kafka), e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Advanced Spring Boot 4: Event-Driven Architecture (Kafka) include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Local Kafka: Your Dev Sandbox
When building applications that use Apache Kafka, you'll need a Kafka cluster to connect to. For development and testing, setting up a local cluster is ideal.
It provides a safe, isolated environment where you can experiment without affecting production systems. This lesson will guide you through setting it up easily with Docker.
Docker and Docker Compose Basics
Docker is a platform for developing, shipping, and running applications in containers. Containers are lightweight, portable, and self-sufficient units.
Docker Compose is a tool for defining and running multi-container Docker applications. You use a YAML file to configure your application's services, then create and start them all with a single command.
Essential Kafka Local Components
A minimal Kafka cluster requires two main components to function:
- Zookeeper: This service manages Kafka brokers, handling leader election, configuration, and coordination. Kafka relies on Zookeeper for its operational state.
- Kafka Broker: This is the core server that stores topics, handles message production and consumption, and replicates data. You'll typically run at least one broker.
Defining Your Services with YAML
We'll define our Kafka setup using a docker-compose.yml file. This file tells Docker Compose which services to run, which images to use, and how they should be configured and networked.
Each service in the file represents a container that will be launched. Let's start building it step-by-step.
Zookeeper in Docker Compose
First, let's define the Zookeeper service. We'll use a standard Zookeeper image and expose its default client port.
version: '3.8'
services:
zookeeper:
image: confluentinc/cp-zookeeper:7.5.0
container_name: zookeeper
ports:
- "2181:2181"
environment:
ZOOKEEPER_CLIENT_PORT: 2181
ZOOKEEPER_TICK_TIME: 2000Here, ports: "2181:2181" maps the container's port 2181 to your host's port 2181.
Kafka Broker in Docker Compose
Next, we add the Kafka broker service. It needs to know how to connect to Zookeeper and also exposes its own ports for clients.
kafka:
image: confluentinc/cp-kafka:7.5.0
container_name: kafka
ports:
- "9092:9092"
environment:
KAFKA_BROKER_ID: 1
KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://localhost:9092
KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
KAFKA_GROUP_INITIAL_REBALANCE_DELAY_MS: 0
depends_on:
- zookeeperdepends_on: zookeeper ensures Zookeeper starts before Kafka.
Your Complete Kafka Setup File
Combining both services, your docker-compose.yml file looks like this:
version: '3.8'
services:
zookeeper:
image: confluentinc/cp-zookeeper:7.5.0
container_name: zookeeper
ports:
- "2181:2181"
environment:
ZOOKEEPER_CLIENT_PORT: 2181
ZOOKEEPER_TICK_TIME: 2000
kafka:
image: confluentinc/cp-kafka:7.5.0
container_name: kafka
ports:
- "9092:9092"
environment:
KAFKA_BROKER_ID: 1
KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://localhost:9092
KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
KAFKA_GROUP_INITIAL_REBALANCE_DELAY_MS: 0
depends_on:
- zookeeperSave this content into a file named docker-compose.yml in an empty directory.
Launching Your Kafka Cluster
Once your docker-compose.yml file is ready, navigate to its directory in your terminal. Then, use the following command to start your Kafka cluster:
docker-compose up -dup: Builds, (re)creates, starts, and attaches to containers for a service.-d: Runs containers in detached mode (in the background).
Docker will download images (if not present) and start Zookeeper, then Kafka.
Confirming Kafka is Running
After running docker-compose up -d, you can check if your services are running correctly:
docker ps: Lists all running Docker containers. You should seezookeeperandkafka.docker logs kafka: Shows the logs for the Kafka container. Look for messages indicating it started successfully, like "started (kafka.server.KafkaServer)".
To stop and remove the containers, use docker-compose down.
Docker Compose Command Check
You've just created a docker-compose.yml file and want to start your Kafka cluster in the background. Which command should you use?
Recap: Local Kafka with Docker
Congratulations! You've learned how to set up a local Kafka cluster using Docker Compose. Here's a quick summary:
- Local Kafka provides an isolated dev environment.
- Docker Compose uses a
docker-compose.ymlfile to define multi-container apps. - A minimal Kafka setup requires Zookeeper and a Kafka Broker.
- The
docker-compose.ymlspecifies images, ports, and environment variables. - Use
docker-compose up -dto start anddocker-compose downto stop your cluster.
Now you have a sandbox to build your Spring Boot Kafka applications!
Domande Frequenti
La lezione «Configurare Kafka in locale con Docker» è gratuita?
Sì — il testo completo di «Configurare Kafka in locale con Docker» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Advanced Spring Boot 4: Event-Driven Architecture (Kafka), passa a CoddyKit PRO. Il corso Advanced Spring Boot 4: Event-Driven Architecture (Kafka) include 4 lezioni in totale.
Cosa imparerò in «Configurare Kafka in locale con Docker»?
Impari a configurare rapidamente un cluster Kafka locale usando Docker Compose, creando un ambiente isolato per sviluppo e test. Eserciti Advanced Spring Boot 4: Event-Driven Architecture (Kafka) con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?
Non è richiesta alcuna esperienza precedente. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Configurare Kafka in locale con Docker»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?
Sì. Ogni lezione Advanced Spring Boot 4: Event-Driven Architecture (Kafka) include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Panoramica dell'architettura di Kafka
- Topic, partizioni e offset
- Configurare Kafka in locale con Docker
- Gruppi di consumer e ribilanciamento