Chapter 1. Setting the Stage
This project continued the Human Capital reporting migration work by replatforming the deployed reporting services from a Compute Engine based setup into a Cloud Run oriented architecture. The main goal was to reduce recurring infrastructure cost, remove dependency on an always-on report server, and keep the reporting flow stable for internal users across the same large report surface that had already been modernized in PRJ06.
This work was delivered in collaboration with Internal Reporting Framework Team and Related Platform Support.
Chapter 2. Carrying the Work
Responsibilities in this project included Reworked the deployed Human Capital reporting setup from Compute Engine into Cloud Run based services, Updated service configuration, report endpoints, and environment routing so the migrated reporting flow could continue without the dedicated server, Adjusted supporting integrations for report generation, export flow, and related Google service dependencies, Validated that report forms and existing business rules still produced consistent output after the infrastructure change, Reduced reliance on always-on infrastructure by moving the workload into a more managed runtime model, and Helped preserve the existing reporting experience while modernizing the operational hosting model behind it.
Chapter 3. What Changed
The project removed the dedicated Compute Engine dependency from the Human Capital reporting platform and replaced it with a more cost-efficient Cloud Run based hosting model. As a result, infrastructure overhead was reduced while the reporting workflow, form coverage, and expected output remained stable for internal users.
Chapter 4. The Problem and the Response
Problem
The reporting system had already been migrated away from Oracle Forms, but the deployed stack still depended on a Compute Engine based server that stayed active continuously. That setup created avoidable infrastructure cost and operational overhead for a reporting workload that could be served through a more managed cloud runtime.
Solution
The solution was to replatform the reporting services into Cloud Run and related managed Google services while preserving the same reporting behavior, form coverage, and business output expected by internal Human Capital users.
Chapter 5. How It Was Built
This project was less about rebuilding report logic from zero and more about modernizing the hosting model behind an already-migrated reporting platform. The challenge was to cut infrastructure cost without breaking report behavior across many existing forms and supporting service dependencies.
Implementation Flow: Existing reporting endpoints, configuration, and environment assumptions are reviewed first so the Compute Engine dependency can be removed safely. The reporting runtime and supporting integrations are reconnected into Cloud Run based services and managed Google components that better match the actual workload pattern. The resulting flow is validated so report generation, export behavior, and business output stay aligned with what internal users already rely on.
Implementation details included Replatformed reporting services from Compute Engine to Cloud Run, Reduced dependency on an always-on dedicated report server, Updated environment configuration and report endpoint routing, Worked with Python based reporting services and existing internal framework behavior, Aligned export and supporting Google service integrations with the new runtime model, and Focused on infrastructure cost efficiency without changing the user-facing reporting intent.
Some implementation details are intentionally generalized because this was an internal enterprise reporting platform.
Chapter 6. Application Flow
Primary Flow: Users continue selecting report parameters through the existing Human Capital reporting forms. Requests are routed into the updated Cloud Run based reporting services instead of the previous dedicated Compute Engine host. The system processes queries, transformations, and export logic, then returns structured report results with the same operational intent as the earlier migrated platform.
