AD482 – Developing Event-Driven Applications with Apache Kafka and Red Hat AMQ Streams — Lesson 3: Kafka Streams, Connectors, Transactions, Error Handling, and Security

Learning Objectives

• Evaluate security, resilience, integration, and exception handling for Kafka Streams, connectors, and transactions.
• Apply error handling and security while preserving reviewable technical evidence.
• Recognize and correct the risk where the design works normally but fails under scale, dependency loss, policy enforcement, or integration delay.

Detailed Topics

• Kafka 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.
• connectors: 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.
• transactions: 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.
• error handling: 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.
• security: 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 streams, connectors, transactions, error handling, and security by tracing the relevant architecture, commands, configuration, messages, and evidence. The walkthrough highlights how the design works normally but fails under scale, dependency loss, policy enforcement, or integration delay and shows how to isolate the cause without masking dependent issues.

Hands-On Exercise

Introduce a controlled boundary condition and test recovery for Kafka Streams, Connectors, Transactions, Error Handling, and Security. 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 Streams in the stated scenario.
• Compare two approaches for error handling 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 security, integration, boundary conditions, and resilience separately, then correlate logs, events, commands, and configuration history. Do not accept the initial assumption that the design works normally but fails under scale, dependency loss, policy enforcement, or integration delay; confirm the cause with a reproducible retest.

Validation Checklist

• The required security, integration, boundary conditions, and resilience 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 Streams, Connectors, Transactions, Error Handling, and Security, 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.