Running critical components requires a completely different mindset when the required uptime is five nines. Can a service even have a 99.999% uptime guarantee? It's easy to promise, but delivering on that is something else. What works at two or three nines can't work when components become critical. The math actually tells us this.

You'll get a full review of how we managed to promise such a high up time, if it is even possible to make it happen, and how they think about it. From this talk attendees will learn key trade-offs in elevating the reliability of their solutions.

Key Takeaways:
* The core components of a highly reliable solution
* Lessons learned in the process
* Architecture strategies to increase the reliability


At Authress, we run a service that has an expected 99.999% SLA. It didn't get there overnight.

There are many reasons to require high uptimes--regulatory needs, critical application dependencies, or in some situations your service could offer life-saving responsibilities. In these circumstances, it becomes critical to get this right, and never let your service go down.

This will be a review of how we’ve architected, built, and maintain a software solution that promises such a high SLA, the frameworks and strategies we’ve established, and what it takes to keep up that commitment.

Key Takeaways:
* The core components of a highly reliable solution
* Lessons learned in the process
* Architecture strategies to increase the reliability