Architecture · 6 min
Workload placement before platform selection
A practical decision sequence for regional applications, data copies, recovery and operating ownership.
A useful cloud discussion starts with the workload, not the product catalogue.
Map the operating locations
List where users, offices, plants, stores, partners and administrators actually work. Separate a legal entity's location from the network location of an application or data copy.
Map every important data copy
Primary data, replicas, logs, backup sets and exported reports may have different retention and placement requirements. Treat each as a distinct design decision.
Record dependencies
Document identity, DNS, databases, file shares, licences, third-party APIs, scheduled jobs, monitoring and administrator access. A workload rarely migrates alone.
Define recovery in business terms
Recovery point objective (RPO) is the acceptable data-loss window. Recovery time objective (RTO) is the target time to restore a service. Neither is a guarantee without a tested design, runbook and agreed assumptions.
Assign operating ownership
For each control and alert, name the provider task, customer task and joint decision. This is the foundation of a workable managed-service scope.
Turn regional requirements into an architecture your teams can review.
Start with workload placement, connectivity, data flows, recovery objectives, migration risk and the full commercial scope.