From the source
Lead story
Ask your AI
Top stories
Models & availability
Latest
Two zones or three? A design framework for zone-resilient Azure workloads
Microsoft's guide presents a design framework for zone-resilient Azure workloads, arguing that zone resiliency should be decided component by component rather than applied uniformly.
It distinguishes between zone-redundant resources managed by Azure and zonal resources that require manual configuration, and provides a decision process based on resource availability, data consistency, and cost.
From the source
Zone resiliency isn’t a single number you apply to a whole workload. The useful question isn’t “how many zones?” but “how many zones does each component need to survive the loss of one?” Decide zone patterns component by component, use service-managed zone redundancy wherever it fits, and reserve three-zone designs for the components that genuinely require a third failure domain.
azure.microsoft.com
Other stories
Amazon · 2 OctSweep thousands of leases for compliance using Amazon Quick and the Adjudicated Query patternAmazon · 2 OctAdd secure Web Search to Claude Desktop with Amazon Bedrock AgentCoreAmazon · 2 OctFine-tune a search agent with multi-turn RL on Amazon SageMaker AI