🧱 Architecture Whiteboard β€” IaaS Β· PaaS Β· SaaS

What happens when you click

🏒 Current state (on-prem)

VMware ESXi clustersHypervisor Β· 3,500 VMs
Hyper-V hostsHypervisor Β· 900 VMs
Oracle RACDatabase Β· 12 TB
Exchange farmEmail Β· 8 servers
MainframeCore ledger

☁️ Future state (cloud)

IaaSAWS EC2 (Nitro hypervisor)
IaaSAzure Virtual Machines
PaaSAmazon RDS for Oracle
PaaSAzure SQL Database
SaaSMicrosoft 365 (Exchange Online)
RetainStay on-prem (for now)
0 / 5 mapped
Drag a component, or click one to read about it.
Mapping results appear here.

Replication flow

Source VMagent installed
➜
Block replicationcontinuous
➜
Staging areacloud subnet
➜
Test launchisolated
➜
Cutover launchproduction
Click a node to learn what it does.

    Deep dive

    How

    • Hypervisor: software that slices a physical host into VMs. ESXi/Hyper-V on-prem; Nitro (AWS) or Azure's host OS in cloud β€” you never see it.
    • IaaS: you keep the guest OS. PaaS: provider keeps OS + engine. SaaS: provider keeps everything but identity/data policy.

    Why

    • Each step up the stack removes undifferentiated toil β€” patching, backups, HA.
    • Shared-responsibility clarity prevents the β€œI thought AWS backed that up” incident.

    When

    • IaaS for speed (wave 1).
    • PaaS when a managed equivalent exists and licensing allows.
    • SaaS for commodity (mail, HR, CRM).

    Pitfalls

    • Oracle licensing on cloud vCPUs (core factor) can double cost β€” check BYOL.
    • Exchange β†’ M365 needs hybrid identity (Entra ID Connect) first.
    • Assuming PaaS removes your backup responsibility entirely β€” you still own retention policy.

    Key ideas

    LayerOn-premIaaSPaaSSaaS
    Facilities, hardware, hypervisorYouProviderProviderProvider
    Guest OS patchingYouYouProviderProvider
    DB engine / middlewareYouYouProviderProvider
    Application codeYouYouYouProvider
    Identity, data classificationYouYouYouYou
    🐍 Python executed on the server (map_component)
    loading…