AD082 – Event-Driven Architecture with Apache Kafka and Red Hat OpenShift Application Services Technical Overview — Lesson 3: Schemas, Connectors, Streams, OpenShift Services, Security, and Observability

Learning Objectives

• Evaluate security, resilience, integration, and exception handling for schema management, Kafka Connect, and stream processing.
• Apply OpenShift services and security and observability 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

• schema management: apply the concept to an architecture team evaluating event-driven integration for loosely coupled digital services, record the relevant settings or decisions, and explain the operational consequence.
• Kafka Connect: apply the concept to an architecture team evaluating event-driven integration for loosely coupled digital services, record the relevant settings or decisions, and explain the operational consequence.
• stream processing: apply the concept to an architecture team evaluating event-driven integration for loosely coupled digital services, record the relevant settings or decisions, and explain the operational consequence.
• OpenShift services: apply the concept to an architecture team evaluating event-driven integration for loosely coupled digital services, record the relevant settings or decisions, and explain the operational consequence.
• security and observability: apply the concept to an architecture team evaluating event-driven integration for loosely coupled digital services, record the relevant settings or decisions, and explain the operational consequence.

Instructor Demonstration

The instructor demonstrates schemas, connectors, streams, openshift services, security, and observability 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 Schemas, Connectors, Streams, OpenShift Services, Security, and Observability. Add verified outcomes to the event-driven architecture brief, service interaction map, technology decision record, and adoption roadmap.

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 schema management in the stated scenario.
• Compare two approaches for OpenShift services and explain the security, reliability, and support trade-offs.
• Decide what evidence must be retained in the event-driven architecture brief, service interaction map, technology decision record, and adoption roadmap 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 event-driven architecture brief, service interaction map, technology decision record, and adoption roadmap 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 Schemas, Connectors, Streams, OpenShift Services, Security, and Observability, explain the observed Red Hat platform behavior, and support the result with a reviewable event-driven architecture brief, service interaction map, technology decision record, and adoption roadmap.