AD482 – Developing Event-Driven Applications with Apache Kafka and Red Hat AMQ Streams — Lesson 4: Testing, Observability, Performance, OpenShift Deployment, and Operations

Learning Objectives

• Operate, troubleshoot, document, and improve testing, observability, and performance.
• Apply OpenShift deployment and operations while preserving reviewable technical evidence.
• Recognize and correct the risk where the technical fix is successful but monitoring, rollback, ownership, or handover remains incomplete.

Detailed Topics

• testing: 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.
• observability: 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.
• performance: 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.
• OpenShift deployment: 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.
• operations: 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 testing, observability, performance, openshift deployment, and operations by tracing the relevant architecture, commands, configuration, messages, and evidence. The walkthrough highlights how the technical fix is successful but monitoring, rollback, ownership, or handover remains incomplete and shows how to isolate the cause without masking dependent issues.

Hands-On Exercise

Run an operational review and produce support-ready evidence for Testing, Observability, Performance, OpenShift Deployment, and Operations. 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 testing in the stated scenario.
• Compare two approaches for OpenShift deployment 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 monitoring, troubleshooting, rollback, ownership, and handover separately, then correlate logs, events, commands, and configuration history. Do not accept the initial assumption that the technical fix is successful but monitoring, rollback, ownership, or handover remains incomplete; confirm the cause with a reproducible retest.

Validation Checklist

• The required monitoring, troubleshooting, rollback, ownership, and handover 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 Testing, Observability, Performance, OpenShift Deployment, and Operations, 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.