// Architecture

The Deployment Stamps pattern is a powerful cloud architecture approach for scaling, resilience, and multi-tenancy. In this episode, Chris Reddington is joined by John Downs — who contributed the pattern to the Azure Architecture Center — to explore how stamping out independent copies of your application stack across regions enables geographic distribution, data sovereignty, isolated failure domains, and deployment rings for staged rollouts. Discover when to use this pattern, how Azure itself relies on it internally, and the key considerations around request routing, cross-stamp querying, and disaster recovery planning.

Moving to Azure? Security has to come first. Chris is joined by cybersecurity expert Andrew Nathan to explore how organisations can build a strong security posture in the cloud — covering Azure Security Center and Secure Score, identity strategy (Azure AD vs. Azure RBAC), multi-factor authentication, threat modelling, Azure Policy and Management Groups for governance, and the evolution of security operations into red team/blue team war gaming. Whether you're starting your cloud journey or course-correcting an existing environment, this episode will help you understand where to begin and how to keep improving over time.

Hybrid cloud is no longer just a transitional state between on-premises and public cloud — for many enterprises, it is the end state. Chris is joined by Thomas Maurer, Senior Cloud Advocate at Microsoft, to explore how Azure Arc, Azure Stack Hub, Azure Stack HCI, and Azure IoT Edge help organisations run workloads wherever they make sense: from data centres and factory floors to the network edge and other cloud providers.

APIs are the connective tissue of modern cloud architectures — but poor API design compounds into technical debt that is expensive to unwind. In this episode, Chris Reddington and Peter Piper explore the full lifecycle of API design: defining versioning contracts up front, modernising legacy APIs using the Strangler and Façade patterns, and securing APIs with JWT tokens, OAuth 2.0, and OIDC. They also cover Azure API Management patterns, circuit breakers, throttling, key rotation with Azure Key Vault, and the DevSecOps practices that keep an API estate healthy at scale.

Moving to the cloud shifts infrastructure spend from capital expenditure (CapEx) to operational expenditure (OpEx)—but only if you think about cost correctly from the start. This episode covers the cloud cost mindset: right-sizing, auto-scaling (scale out vs scale up), compute resource consolidation, governance through resource tagging and policy, pricing calculators, reserved instances, and how to build cost awareness into your architecture from day one.

Every cloud project starts with requirements. In this episode, Chris explores the critical pillars of cloud architecture: resilience (SLA, RTO, RPO, MTTR, MTBF), scalability, performance, and cost. Learn why defining requirements upfront—before drawing architecture diagrams—is essential, and how the same on-premises thinking about availability translates directly into the cloud.

Cloud design patterns are abundant and well-documented on the Azure Architecture Center — from established patterns like cache-aside and materialized view to cloud-native ones like circuit breaker and health endpoint monitoring. This Azure Mythbusters episode tours the full pattern catalogue and deep-dives four key patterns: cache-aside, circuit breaker (open/half-open/closed states), health endpoint monitoring, and materialized view in CQRS/event sourcing scenarios.

Cloud is not inherently more expensive than on-premises once you account for hardware depreciation, power, cooling, and network costs — but it requires designing cost into your architecture from the start. This Azure Mythbusters episode examines fixed versus variable cost envelopes, auto-scaling strategies for spiky workloads like Black Friday traffic, the IaaS/PaaS/serverless cost spectrum, and cost as an implicit sixth pillar alongside the five pillars of software quality.

Moving workloads to Azure does not eliminate management decisions — scalability, resilience, and high availability all require deliberate configuration. This Azure Mythbusters episode contrasts scale-out via VM Scale Sets and auto-scale rules with scale-up by increasing VM SKU size, explains availability sets and availability zones, and shows how PaaS services like Azure Functions still require you to choose the right plan and design cross-region resilience with Traffic Manager.

Requirements remain essential when migrating to or building on Azure — from availability SLAs and RPO/RTO targets to compliance, data sovereignty, and cost. This Azure Mythbusters episode uses composite SLA calculations and Azure Architecture Center reference architectures to show how under- or over-specifying requirements directly shapes your design, region strategy, and overall cost.