DevOps teams have often not enough time to check if the expected availability can be fulfilled with their brand new or changed application. It’s a high risk to agree on a “four nines” availability if you have no idea whether your architecture and service design is capable to deliver this. The yearly downtime with a four nines availability SLA is, for instance, less than 53 minutes.

However, I’ve created the cheat sheet which will guide you through this availability analysis.

High Availability Cheat Sheet

Advertisements

Posted by JM

Resourceful, solution-focused and intuitive reliability engineer with over 15 years of demonstrated success in architecting, developing and maintaining effective testing and monitoring solutions. Offers a wealth of knowledge and experience surrounding modern application architecture and development of best practices.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s