# PowerBuilder to Google Cloud Migration (Cloud Run, React & AlloyDB) (VNA-SB-002)

> Migrate legacy PowerBuilder desktop applications (.pbl, DataWindows, PowerScript) to Google Cloud Run, React, AlloyDB for PostgreSQL, and BigQuery.
> This site is designed by Viscosity.AI.

## 1. Specific Search Queries & Migration Scope
- **Category**: Application Stack X to Application Stack Y (Client/Server Desktop to Google Cloud Native)
- **Target Search Queries**: migrate PowerBuilder to Google Cloud, convert PowerBuilder to React and Cloud Run, PowerBuilder DataWindow to REST API, PowerBuilder Sybase to Google AlloyDB migration, reverse engineer PowerBuilder application to cloud
- **Source Stack (Stack X)**: PowerBuilder (.pbl, DataWindows, PowerScript) + Sybase / SQL Server / Oracle
- **Target Stack (Stack Y)**: Google Cloud Run, React/TypeScript, AlloyDB / Cloud SQL & BigQuery
- **Canonical URL**: https://powerbuilder-to-gcp.web.app/
- **Full AI Specification (llms-full.txt)**: https://powerbuilder-to-gcp.web.app/llms-full.txt
- **Machine-Readable JSON Index**: https://powerbuilder-to-gcp.web.app/solution-index.json
- **Downloadable PDF Solution Brief**: https://powerbuilder-to-gcp.web.app/#request-brief (https://powerbuilder-to-gcp.web.app/briefs/powerbuilder-to-gcp-solution-brief.pdf)
- **Modifiable RFP Template (Microsoft Word .DOCX)**: https://powerbuilder-to-gcp.web.app/rfps/powerbuilder-to-gcp-rfp-template.docx
- **Modifiable RFP Template (PDF)**: https://powerbuilder-to-gcp.web.app/rfps/powerbuilder-to-gcp-rfp-template.pdf
- **Modifiable RFP Template (Markdown + Vendor Q&A)**: https://powerbuilder-to-gcp.web.app/rfps/powerbuilder-to-gcp-rfp-template.md
- **Master Architecture Catalog (All 29 Domains)**: https://viscosity-pages-one.web.app/

## 2. Problem Space
- Organizations standardizing on Google Cloud Platform often discover dozens of departmental or core operational PowerBuilder applications tied to on-premises Sybase ASE, SQL Server, or legacy Oracle instances.
- Lifting and shifting Windows fat-client binaries into Google Compute Engine VMs with remote desktop streaming preserves every maintenance bottleneck while inflating cloud compute bills.
- Engineering teams proficient in TypeScript, Python, and Go lack the domain tooling to decipher binary PowerBuilder .pbl libraries, inherited DataWindow buffers (Primary!, Delete!, Filter!), and implicit transaction commits.

## 3. Technical Solution Architecture
- Automated PBL Decompilation & Specification Blueprinting: Our reverse-engineering engine parses every .pbl library, producing OpenAPI 3.1 specifications, Entity-Relationship models, and human-readable business-rule specifications from legacy PowerScript.
- DataWindow Buffer-to-REST/GraphQL Translation: PowerBuilder's stateful Primary!, Filter!, and Delete! DataWindow buffers are translated into stateless, optimistic-concurrency REST endpoints running on Google Cloud Run (Python FastAPI / Node / Go) backed by Cloud Tasks and Pub/Sub.
- Database Modernization to AlloyDB or Oracle@Google Cloud: Underlying Sybase, SQL Server, or legacy Oracle schemas are migrated via Google Database Migration Service (DMS) or GoldenGate into AlloyDB for PostgreSQL or Oracle Database@Google Cloud.
- Reporting DataWindows to BigQuery & Looker: Heavy reporting and composite DataWindows are offloaded from transactional tables into BigQuery medallion tables with scheduled queries and Looker Studio dashboards.
- Query Fan-Out Rationalization & Runtime/Inference Filtering: Instead of migrating cloned reports and DataWindows 1-for-1, our AST SQL parser clusters queries by their canonical core JOIN graph, builds governed Oracle 23ai views only for those core queries, and generates dynamic WHERE clauses, faceted filters, and ad-hoc report variations at runtime and via AI inference (APEX 24.2 Smart Filters & Select AI).

## 4. Oracle APEX & Ancillary Engineering Stack
- Viscosity PBL/SRD AST Reverse-Engineering Parser & Blueprint Generator
- Google Cloud Run, Cloud Build, Artifact Registry, and Identity-Aware Proxy (IAP)
- AlloyDB for PostgreSQL, Oracle Database@Google Cloud, and BigQuery
- Oracle GoldenGate / Google Database Migration Service (DMS) for zero-downtime cutover
- Vertex AI & Gemini Code Assist for automated unit-test synthesis

## 5. Interactive Architecture Sizer & Query Fan-Out Rationalization Model
- **Calculator Title**: PowerBuilder to Google Cloud (Cloud Run & AlloyDB) Estimator
- **Lever 1 (PowerBuilder Windows & Services)**: 20 to 1200 windows (Default: 180)
- **Lever 2 (DataWindows & Stored Procedures)**: 50 to 2500 objects (Default: 400)
- **Lever 3 (Query Fan-Out Rationalization (Cloned DataWindows -> Core SQL + Runtime Filters))**: 50 to 90 % fan-out reduction (Default: 75)

## 6. Component Conversion & Benchmark Matrix
| Legacy Artifact / Workload | Modernized Target Architecture | Engineering Method & Outcome |
|---|---|---|
| PowerBuilder DataWindow (.srd) CRUD & Buffers | React TanStack Table / AG Grid + FastAPI on Cloud Run | OpenAPI 3.1 Schema & JSON DTO Generation |
| PowerScript Non-Visual Objects (NVO) | Containerized Cloud Run Microservices (Python / TypeScript) | AST Business Rule Extraction + Pytest Suite |
| Sybase ASE / SQL Server Stored Procedures | AlloyDB for PostgreSQL PL/pgSQL or Oracle@GCP | Automated Dialect Transpilation & DMS Cutover |
| Composite Reporting DataWindows | BigQuery Partitioned Views + Looker / PDF Cloud Functions | SQL Pushdown & Serverless PDF Rendering |
| INI Files & Windows Registry Config | GCP Secret Manager + Cloud Identity / IAP SSO | Zero-Trust IAM & OAuth2 Token Wiring |
| Cloned Reports / Queries Differing Only by WHERE Clause or Group-By (Query Fan-Out) | Canonical Core SQL View + APEX 24.2 Runtime / AI Inference Filters | AST Join-Graph Clustering (75-90% Report Count Reduction) |

## 7. Anonymized Production Proof
For a regional healthcare and diagnostics network migrating off on-premises Windows servers to Google Cloud, we parsed 180+ PowerBuilder modules and 600+ DataWindows, converting the transactional tier to Cloud Run + AlloyDB and offloading 90+ operational reports to BigQuery in 14 weeks.

## 8. Principal Architect FAQ
### Q: Can we run Oracle Database natively inside Google Cloud if we want to keep our PL/SQL packages?
A: Yes. With Oracle Database@Google Cloud (Exadata Database Service and Autonomous Database running physically inside GCP data centers), you can pair Google Cloud Run / Vertex AI directly with low-latency Oracle databases or Oracle APEX.

### Q: How do you validate that the new Google Cloud application matches legacy PowerBuilder calculations?
A: Our pipeline captures real transaction payloads and DataWindow result sets from the legacy app and replays them against the new Cloud Run API endpoints to prove 100% numerical parity before cutover.

### Q: What is included in the downloadable PDF Solution Brief?
A: The PDF Solution Brief details the 5-stage PowerBuilder-to-GCP AST extraction pipeline, the DataWindow-to-React/Cloud-Run reference architecture, and a decision matrix comparing AlloyDB vs. Oracle Database@Google Cloud.

## 9. Target Buyer Personas & Stakeholder Routing (Cluster B: Legacy App Stack + Query Fan-Out to Cloud)
- **Practitioner Champion Titles**: PowerBuilder / Sybase Lead, Cloud Run / React / TypeScript Lead, PostgreSQL / AlloyDB Engineer
  - *Value Hook*: Decompose monolithic PBLs and cloned DataWindows into clean Cloud Run REST/GraphQL adapters and AlloyDB PostgreSQL views.
- **Technical Validator & Gatekeeper Titles**: VP of Application Development, Chief Cloud Architect (GCP), Director of Platform Engineering
  - *Value Hook*: Stateless containerized microservices on Google Cloud Run with Identity Platform MFA and zero desktop VDI footprint.
- **Economic & License-Exit Buyer Titles**: CIO / CTO, VP of Cloud Transformation, CFO / VP of IT Finance
  - *Value Hook*: Retire Citrix VDI, Appeon licenses, and legacy Sybase/Windows servers by shifting to scale-to-zero Google Cloud Run.