liveBook · Manning

ZooKeeper

As explained in Quarkus in Action

Apache ZooKeeper is a distributed coordination service that provides shared configuration, naming, synchronization, and metadata-management primitives.

ZooKeeper is a coordination service used by the Strimzi Kafka platform for metadata management in a production-style car-rental deployment. It appears as an additional infrastructure container when Redpanda is replaced with Strimzi Kafka. section 11.1.1

Production infrastructure deployment

A Docker Compose deployment starts separate Kafka and ZooKeeper containers alongside application databases, messaging, identity, tracing, metrics, and dashboard services. The infrastructure can be started with docker compose -f docker-compose-files/docker-compose-infra.yml up and removed with the corresponding down command. section 11.1.1

Figure 11.2 The Acme Car Rental production with all dependent services
figure

Use the deployment figure to locate ZooKeeper within the complete production topology and understand its relationship to Kafka and dependent services. section 11.1.1

How Quarkus in Action covers it

How deep it goes
Identifies ZooKeeper’s deployment role and container placement but does not explain its coordination internals or configuration.
Examples
Uses a separate zookeeper container in a Docker Compose topology containing Kafka and supporting infrastructure services.
What you can do after
Operate a local production-style Kafka infrastructure deployment that includes ZooKeeper as a supporting container.
How it connects
Connects ZooKeeper with Apache Kafka, the Strimzi Kafka platform, Docker Compose, and Kafka metadata management.

Also explained in

Compare how 3 books explain ZooKeeper →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.