DO092 – Developing Cloud-Native Applications with Microservices Architectures — Lesson 4: DevOps Delivery, Platform Choices, Trade-offs, Governance, and Roadmap

Learning Objectives

• Operate, troubleshoot, document, and improve DevOps delivery, platform choices, and trade-offs.
• Apply governance and roadmap 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

• DevOps delivery: apply the concept to an application architecture team evaluating how to decompose and modernize a traditional enterprise application, record the relevant settings or decisions, and explain the operational consequence.
• platform choices: apply the concept to an application architecture team evaluating how to decompose and modernize a traditional enterprise application, record the relevant settings or decisions, and explain the operational consequence.
• trade-offs: apply the concept to an application architecture team evaluating how to decompose and modernize a traditional enterprise application, record the relevant settings or decisions, and explain the operational consequence.
• governance: apply the concept to an application architecture team evaluating how to decompose and modernize a traditional enterprise application, record the relevant settings or decisions, and explain the operational consequence.
• roadmap: apply the concept to an application architecture team evaluating how to decompose and modernize a traditional enterprise application, record the relevant settings or decisions, and explain the operational consequence.

Instructor Demonstration

The instructor demonstrates devops delivery, platform choices, trade-offs, governance, and roadmap 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 DevOps Delivery, Platform Choices, Trade-offs, Governance, and Roadmap. Add verified outcomes to the microservices suitability assessment, service-boundary map, architecture risks, and modernization 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 DevOps delivery in the stated scenario.
• Compare two approaches for governance and explain the security, reliability, and support trade-offs.
• Decide what evidence must be retained in the microservices suitability assessment, service-boundary map, architecture risks, and modernization roadmap 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 microservices suitability assessment, service-boundary map, architecture risks, and modernization 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 DevOps Delivery, Platform Choices, Trade-offs, Governance, and Roadmap, explain the observed Red Hat platform behavior, and support the result with a reviewable microservices suitability assessment, service-boundary map, architecture risks, and modernization roadmap.