Understanding of High Availability NFR (Non Functional Requirement)

Connect with

Understanding of HA ( High Availability ) of non functional requirement is not easy, it’s art with science. Being an architect, it is very important to understand cost vs acceptable downtime, i mean to say how much cost you are going to invest of servers and your acceptance downtime before committing to the stakeholder of your application.

High availability requires less human intervention to restore operation in complex systems, the reason for this being that the most common cause for outages is human error.

Availability Percentage and Downtime in a Year

Availability is usually expressed as a percentage of uptime in a given year. On high level following are the facts which

[table “” not found /]

if you go through the above tabular calculation data you can understand how much availabity you are required in your application and how much redundancy and cost have to pay for this Non-Functional requirement.
In general, the number of nines is not often used by a network engineer when modeling and measuring availability because it is hard to apply in formula.


1. In a year, what is the maximum number of days of downtime you can have and still claim >99% uptime?

a. less than 1 days
b. 2 days
c. 3 days
d. 4 days
e. 5 days

Answer: 3 days.


  1. Wiki

Connect with

7 thoughts on “Understanding of High Availability NFR (Non Functional Requirement)

  1. great info, I like this stats of 9 . please write this type of post in future I’ will come here to read and grasp..

  2. Well wishes one of the highest quality thing We can stumble upon in my life.
    you do in order to create tech fun for training http://www.delhiguru.in they engage in battles and wars accomplish
    control from the territory Rachel Whatever you want to watch, ..

  3. Pingback: rakesh
  4. Pingback: Swati

Leave a Reply

Your email address will not be published. Required fields are marked *