Fork 01
Move it at all?
What actually happens during a cloud migration and whether the case for doing it holds up under scrutiny.
work down the list until one of them stings
The worksheet
Every guide at this fork answers one row. Work down the left column until something you believe stops being true.
| What you think | What is actually true |
|---|---|
| "Moving to the cloud" is a change of address. | Compute, networking, storage and the whole dependency chain change shape. The operational version of that story, not the marketing one.What Moving to the Cloud Actually Means → |
| Move it as it stands now, redesign it later. | A workload moved without redesign usually buys cloud cost without cloud benefit — and "later" rarely arrives.The Lift-and-Shift Trap → |
| Their datacentre is our datacentre, only bigger. | Power redundancy, network topology and hardware refresh cycles all differ — and only some of that difference ever reaches a tenant.How a Hyperscaler's Datacentre Differs from Yours → |
| Security is the provider’s job. | The line moves with each service model, and most incidents land on the tenant’s side of it.Shared Responsibility, Drawn Plainly → |
The 4 guides, in reading order
Every guide →
What Moving to the Cloud Actually MeansA plain-mechanics explainer of what physically and logically changes when workloads move to a hyperscaler — compute, networking, storage, and the dependency chain. Written to replace the marketing version of this story with the operational one.By the ExtraSys desk · Move it at all? · 5 min read
The Lift-and-Shift TrapAn argument about why moving a workload without redesigning it typically produces the worst of both worlds — cloud cost without cloud benefit. Walks through what typically goes wrong and why it keeps happening.By the ExtraSys desk · Move it at all? · 3 min read
How a Hyperscaler's Datacentre Differs from YoursA comparative piece on physical and operational differences — power redundancy, network topology, hardware refresh cycles, and what those differences do and do not mean for a tenant. Not a pitch for cloud; a factual contrast.By the ExtraSys desk · Move it at all? · 3 min read
Shared Responsibility, Drawn PlainlyA walk-through of the shared responsibility model — what the provider owns, what the tenant owns, and where most incidents fall — using the three main service models as the frame. Avoids presenting any division as sufficient security.By the ExtraSys desk · Move it at all? · 2 min read