Cloud · DevOps · Architecture

Architecture with the bill attached

Where the workload runs is an architecture decision and a financial one, and they are usually made by different people who never compare notes. This is cloud, colocation and on-premise work written with both in view — placement, migration, the scaffolding that has to exist first, and the diagrams that quietly stopped being true.

Cloud Architecture Colocation Placement Economics Migration Infrastructure as Code Scaffolding Diagrams That Hold Cost Modelling

The right answer applied everywhere is the wrong answer — placement is a per-workload decision with a number attached.

Most migration regret traces to a decision made once and applied uniformly: everything to the cloud, or everything back. The writing here keeps landing on the same correction — the unit of decision is the workload, the evidence is the run-rate and the depreciation schedule, and the architecture diagram is only useful if somebody checks that the lines still describe what the system does.

The frame

Four questions before anything moves

Read the scaffolding piece →

What is it, really

Steady-state or spiky, latency-bound or throughput-bound, regulated or not. The workload's own shape decides where it belongs, and the shape is measurable.

What does it cost where

Run-rate against capital, depreciation against a lease, and the egress nobody modelled. The comparison is arithmetic, not preference.

What has to exist first

Pipelines, environments, observability and the ability to roll back. Scaffolding built after the move is built during the incident.

What does the diagram claim

An architecture drawing is a set of assertions about the system. Most of them go stale silently, and the lines go wrong before the boxes do.

Flagships

What has to be true before you move anything

Study · Delivery · Reference

The Scaffolding Comes First

The environments, pipelines and rollback paths that have to exist before a migration is a migration rather than a hope. Written from the order these things actually get discovered in.

DeliveryMigrationWPR-CLD-001

Read the study

Study · Architecture · Reference

UML: The Boxes Were Right and the Lines Were Wrong

Architecture diagrams as assertions that can be checked, and what happens when nobody checks them: the boxes survive reorganisation and the relationships between them quietly stop being true.

ArchitectureModellingWPR-CLD-002

Read the study

Why it fits

Why placement is the through-line

Both sides of the decision

Held the architecture seat and the budget seat, frequently in the same meeting, which is where the disagreement between them becomes visible.

Data centre and cloud, not one camp

Colocation and owned hardware are not nostalgia and the cloud is not a default. The interesting work is knowing which workload belongs where and proving it.

Regulated placement

Data residency, PHI and the question of what leaves the building change the answer before cost does, and they are constraints these systems were built under.

The money is in the writing

Capital versus operating, depreciation schedules and vendor renewals appear throughout, because that is what the placement conversation is actually about.

Field notes

Cloud, DevOps & architecture writing

See all →

See all cloud, devops & architecture writing →

Engage

Deciding where something should run?

Placement and migration review with the arithmetic shown — run-rate, depreciation, residency and the scaffolding that has to be in place before anything moves.

Start a conversation Read the background

This site: HTTPS only · no third-party trackers · no analytics cookies · security.txt