As per wiki definition,
“Business continuity encompasses a
loosely defined set of planning, preparatory and related activities which are
intended to ensure that an organization’s critical business functions will
either continue to operate despite serious incidents or disasters that might
otherwise have interrupted them, or will be recovered to an operational state
within a reasonably short period.”
During deployment
·
Our business should continue with existing
production environment and customers should be able to operate and work with
our products without any interruption
Once deployment is completed
·
Customer should be able to see the changes in
the build and able to operate with our products seamlessly
Business continuity also means that customers should able to
operate with our products in case of deployment failures. We should identify
the time taken for disaster recovery during hot upgrade deployment in case of
deployment failures.
Business continuity
can’t be simulated with manual testing alone. In Production, we are not sure
how many customers are using our products, what the load on production is and
what the customer user cases are. We can automate Business continuity tests by continuously
running the tests before and during upgrade deployment. We should make sure that none
of the automated tests should fail during upgrade deployment because of
deployment issues. We are calling this as Business Continuity/zero downtime testing.
No comments:
Post a Comment