Achieving Always On: Introducing changes without breaking the availability promise

Make non-disruptive changes while delivering innovation

From the developerWorks archives

Bertrand Portier and Scott Simmons

Date archived: December 1, 2016 | First published: December 23, 2014

New services are being designed today and delivered with 100% availability. If you aren't designing and delivering services with 100% availability, your competitors are and they are raising expectations for the industry. Always On requires a radically different approach to how a service is developed, how it is implemented with redundancy, how it is delivered, and how it is managed with alternate processes and procedures. A different method is needed, one that leverages redundancy for testing, verification, and built-in revert capability.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=DevOps, Rational
ArticleID=994355
ArticleTitle=Achieving Always On: Introducing changes without breaking the availability promise
publish-date=12232014