Episode 8 - Design for Availability

published 7 years ago by Microsoft

In a world where dependent services and platforms are not 100% available, architects must embrace that given enough time and pressure, all things will fail.This session, delivered by Mark Simms, will explore how to design for failure, understanding the impact and design choices for distributed services. This session will cover failure at node, service, and regional levels.

Fail safe guidance for resilient cloud architectures. Developed by Microsoft services. And the as your customer advisory team. So far we've talked a lot about everything except for resilience and everything except for availability. There's a reason for that. If your site as 100 percent uptime and conserve 0 users. My hypothesis is that you actually have no resilience and no availability. So you cannot separate scalability availability manage. The iron triangle that will actually let you run services at scale even if your skills relatively small man. So we're taking our talk about all the ways things tend to break and approaches for mediating failure and working. Little bit of philosophy mostly implementation. So. We'll talk about dependencies without my failure modes written about how design for failure. Which is really a way of saying ...

more episodes from FailSafe: Building Scalable, Resilient Cloud Services