Co-authored by @Carlos Chivardi and @Brian Hall
This blog post is the third of three posts that explains the self-healing check and liveness probe feature of IBM Sterling Integrator Certified Containers (SICC), running on Red Hat Open Shift (RHOS).
Read the second post here - IBM Sterling Integrator Certified Containers: Self-healing Scenario (Part 2)
This blog post series is divided into these topics:
- SICC Liveness Overview
- How SICC self-healing works
- Benefits of self-healing feature in SICC
In this blog post we will cover the benefits of self-healing feature in SICC.
As shared in the first part of this blog series, unplanned outages could result in major disruptions in an organization’s supply chain operation which may result in significant reduction of profits and lost trust with trading partners, including customers and suppliers.
A faster response to business-affecting errors or downtime could minimize these losses.
SICC’s self-healing check and readiness probe leverages an agile response that increases reliability and redundancy.
How do you determine that an organization needs SICC?
- The organization’s outage costs can disrupt the business bottom line
- The organization’s Sterling Integrator/Secure File Gateway (SFG) is a mission critical application
- An outage of one hour of more can lead to significant effort to remediate
The key benefits of SICC include:
- Removing a “Single point of failure”
- Increase in efficiencies and add zero down time for preventive and corrective maintenance
- Continuous monitoring.
Finally, you may not be able to control all the factors and variables in an environment, but how you respond in terms of speed, efficiency and effectiveness to an exceptional situation can determine the success or failure of your organization.
Read previous blogs of the Self-healing series:
IBM Sterling Integrator Certified Containers: Self-healing Scenario (Part 1)
IBM Sterling Integrator Certified Containers: Self-healing Scenario (Part 2)