What a room of engineers asked me about realtime resilience
Blog post from Ably
Ably’s resilience strategy, presented at the AWS Cloud Resilience Roadshow in Dublin, treats dependability as encompassing performance, data integrity, reliability, and availability rather than simple uptime. Its architecture is designed to withstand failures across CDNs, DNS, domains, instances, and regions by combining infrastructure redundancy with SDK-level fallback endpoints on separate domains and DNS providers. Semi-autonomous regions can absorb traffic from unhealthy sites, while clients can reconnect to alternate regions and resume sessions with missed messages delivered in order. To reduce the likelihood of a global outage, Ably uses gradual deployments, versioned and reversible configuration changes, independent regional operation, spare capacity, and flexibility across multiple instance types. The platform provides both regional realtime ordering and canonical global ordering through message identifiers, reducing the need for customers to implement their own sequencing and recovery logic. Availability is measured from the customer perspective through synthetic clients in every production region, percentile-based alerts, SLA degradation thresholds, and independent external monitoring, with disaster-recovery drills using the same automation as real incidents.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.