Harbor Parcel needs an event pipeline for its fulfillment team. Build a durable topic, publish the creation and shipping lifecycle without a retry duplicate, process the events and capture a healthy consumer handoff. All names and records are fictional.
Carry the cluster forward through eight dependent changes. Each step starts from your previous result, including the partition logs and consumer progress. The final deliverable is a durable two-event pipeline with a consumer that processed the records and a metrics snapshot that proves its current health. Inspect before changing settings, and preserve the earlier work. These tasks use explicit local controls for replication, event production and business processing. They do not connect to a real broker or a customer system. A zero-lag chart alone is not the deliverable: the processed evidence and delivery policy must also remain correct.
Inspect the topics, partition logs and group offsets before changing the cluster.