AD482 – Developing Event-Driven Applications with Apache Kafka and Red Hat AMQ Streams — Lesson 1: Kafka and AMQ Streams Architecture, Topics, Partitions, Replication, and Clients

Learning Objectives

• Interpret the architecture, dependencies, and expected behavior of Kafka architecture, AMQ Streams, and topics and partitions.
• Apply replication and client libraries while preserving reviewable technical evidence.
• Recognize and correct the risk where a hidden prerequisite causes the first configuration step to produce an incomplete result.

Detailed Topics

• Kafka architecture: apply the concept to a development team building reliable event-driven services on Red Hat OpenShift, record the relevant settings or decisions, and explain the operational consequence.
• AMQ Streams: apply the concept to a development team building reliable event-driven services on Red Hat OpenShift, record the relevant settings or decisions, and explain the operational consequence.
• topics and partitions: apply the concept to a development team building reliable event-driven services on Red Hat OpenShift, record the relevant settings or decisions, and explain the operational consequence.
• replication: apply the concept to a development team building reliable event-driven services on Red Hat OpenShift, record the relevant settings or decisions, and explain the operational consequence.
• client libraries: apply the concept to a development team building reliable event-driven services on Red Hat OpenShift, record the relevant settings or decisions, and explain the operational consequence.

Instructor Demonstration

The instructor demonstrates kafka and amq streams architecture, topics, partitions, replication, and clients by tracing the relevant architecture, commands, configuration, messages, and evidence. The walkthrough highlights how a hidden prerequisite causes the first configuration step to produce an incomplete result and shows how to isolate the cause without masking dependent issues.

Hands-On Exercise

Build a baseline and capture the initial state for Kafka and AMQ Streams Architecture, Topics, Partitions, Replication, and Clients. Add verified outcomes to the Kafka application repository, event contracts, automated tests, and OpenShift deployment portfolio.

1. Confirm the scope, versions, access, dependencies, and success criteria.
2. Perform the workflow while recording commands, settings, output, and platform events.
3. Test one expected case and one controlled exception specific to this lesson.
4. Retest the correction and document ownership, rollback, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences Kafka architecture in the stated scenario.
• Compare two approaches for replication and explain the security, reliability, and support trade-offs.
• Decide what evidence must be retained in the Kafka application repository, event contracts, automated tests, and OpenShift deployment portfolio before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check architecture, access, dependencies, and starting conditions separately, then correlate logs, events, commands, and configuration history. Do not accept the initial assumption that a hidden prerequisite causes the first configuration step to produce an incomplete result; confirm the cause with a reproducible retest.

Validation Checklist

• The required architecture, access, dependencies, and starting conditions were checked and recorded.
• The normal path and a course-specific exception were tested.
• The Kafka application repository, event contracts, automated tests, and OpenShift deployment portfolio links conclusions to commands, configuration, logs, or other objective evidence.
• Corrective actions, rollback steps, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply Kafka and AMQ Streams Architecture, Topics, Partitions, Replication, and Clients, explain the observed Red Hat platform behavior, and support the result with a reviewable Kafka application repository, event contracts, automated tests, and OpenShift deployment portfolio.