What can we do about the dismal uptime of typical applications? Apply these Stability Patterns to contain damage, recover from shocks, and survive disasters.
Faults are inevitable, but failures are not. There are common antipatterns that allow faults to escalate into failures. These are commonly recreated structures that exacerbate problems. In this talk, we’ll look at patterns we can apply to achieve stability in the face of faults: partial failures, overloads, and slow responses. These patterns create resilience for your system. They combat entire classes of failure modes, making your system robust against even unforeseen problems.
I’ve been a professional programmer and architect for over 20 years. In that time, I’ve delivered systems to the U. S. Government, the military, banking, finance, agriculture, and retail industries. Along the way, I have shared my painfully-won experience by mentoring, writing, and speaking.
My work has spanned domains as diverse as B2B exchanges, retail commerce sites, travel and leisure sites, an information brokerage, and applications for the military and intelligence communities.
In 2007, the Pragmatic Programmers published my book Release It! Design and Deploy Production-Ready Software. Most books on software architecture and design aim for QA. “Release It!” is all about surviving the real world.
For information on exhibition and sponsorship opportunities at the conference, contact Gloria Lombardo at firstname.lastname@example.org
For media partnerships, contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at email@example.com
View a complete list of Velocity contacts