eBizon CloudSign in

Architecture reference pack · ARC

OCI Architecture Reference Pack

This reference pack brings together the target end-state, the consolidated master architecture and the governed multi-cloud extension strategy. Use it after reading the playbook guidance to understand the full solution, validate design decisions and tailor the architecture for a customer programme.

1. End-State Architecture

The End-State Architecture provides the two capstone views of the steady-state Oracle Cloud estate: the full-landscape logical architecture and the technical infrastructure topology. Fusion remains the system of record, while OIC, ATP, FDI, OAC and VBS operate inside the governed OCI platform; retired legacy systems remain only as controlled historical sources.

  • Five logical layers cover users and channels, Fusion business applications, integration and APIs, data and analytics, and cross-cutting platform security and governance.
  • Eight catalogued flows define approved identity, API, batch, event, file, analytics, deployment and audit paths.
  • The infrastructure view separates Oracle-managed Fusion services from customer VCNs and maps environments, shared services, Security Zones, a secondary-region DR reserve and authoritative connectivity controls.
    • End-state rule.Fusion pods never sit inside customer VCNs. Integration uses approved REST, SOAP, FBDI, HDL and event paths over Oracle service networking, with default-deny IAM and network controls.

    2. Master Architecture Document

    The Master Architecture Document is the single consolidated reference for the programme. It defines what the estate contains and how its major domains fit together, while the detailed playbook volumes remain the implementation guides for each domain.

    DomainWhat the master document establishes
    Platform foundationSolution and infrastructure architecture, landing zone, governance, environments and workload placement.
    Applications and dataFusion, OIC integration, FDI/OAC analytics, ATP, master data, ETL and migration boundaries.
    Protection and operationsIdentity, security services, approved network and access flows, observability, FinOps and evidence expectations.
    Delivery and continuityTerraform delivery through GitHub and Azure DevOps, drift control, Full Stack DR, manual DR and multi-cloud extension.
    Authority model.Use the master document as the authoritative WHAT for the estate and the relevant deep-dive volume as the HOW. Decisions and exceptions remain subject to the shared governance controls and approval process.

    3. Multi-Cloud Extension Strategy

    The Multi-Cloud Extension Strategy explains how OCI becomes the anchor in a governed estate spanning Azure, AWS and Google Cloud. The approach extends the existing governance model rather than creating separate standards for each cloud.

  • Microsoft Entra ID remains the single identity plane, with cloud-native federation and no routine local users.
  • Fusion-adjacent integration, master data, staging and FDI workloads remain on OCI because of data gravity and Oracle service-network adjacency.
  • Every cloud must reach governance parity before workloads arrive: landing zone, policy and tag mapping, SIEM feed, pipeline identity, CIDR allocation and cost controls.
  • Workload placement follows a recorded decision table, not team preference; cross-cloud flows are registered, secured, observable and reviewed for egress cost.
    • PhaseOutcome
    P0 — IdentityFederated access and keyless pipeline identity across all cloud consoles.
    P1 — Governance parityEquivalent guardrails, tags, budgets, drift checks and one security monitoring queue.
    P2 — Network fabricNon-overlapping addresses, hub connectivity, private DNS and registered flows.
    P3 — First workloadsBusiness-driven pilots delivered through the approved paved road.
    P4 — Unified operationsOne inventory, consolidated FinOps and quarterly multi-cloud governance review.
    Tailoring note.The supplied Word files are generic v1.0 drafts. Replace placeholders and any retained example organization, tenancy, network or environment names before customer use.

    OCI End-State Architecture (v1.0)

    Capstone logical and infrastructure views for the steady-state Fusion and OCI estate, including the flow catalog, environment inventory, connectivity matrix, resilience and growth paths.

    DOCX · 1190 KB

    Download template

    OCI Master Architecture Document (v1.0)

    Consolidated architecture reference spanning solution, infrastructure, landing zone, workloads, OIC, FDI, data, security, operations, FinOps, delivery pipelines, disaster recovery and multi-cloud.

    DOCX · 5324 KB

    Download template

    OCI Multi-Cloud Extension Strategy (v1.0)

    Governed strategy for extending the OCI anchor estate to Azure, AWS and Google Cloud through one identity plane, governance parity, controlled placement and phased adoption.

    DOCX · 261 KB

    Download template