Introduction to high availability
Sterling™ Order Management System Software application is often deployed in an integrated network of external systems and business partners to form a cohesive business ecosystem. Prolonged application or system outages can have significant business consequences.
Approaches can be taken to increase the resiliency of Sterling Order Management System Software to environmental, hardware, or software faults or failure. Techniques and architectural patterns can minimize the impact on the overall ecosystem in the event of a planned or unplanned Sterling Order Management System Software system outage. At the same time, pragmatic approach to availability recognizes that one cannot implement high availability techniques at the detriment of other architectural considerations such as capital cost, ongoing total cost of ownership, or manageability.
Assumptions and requirements
If your Sterling Order Management System Software configuration supports a large number of users from the Web, your wide-area network deployment must be configured in such a way that single (or multiple) faults do not cause an outage.
In today's connected world, security attacks and security fraud is on the rise. Preventing security hacks from taking down systems is a large and complex area that warrants detailed study and is not addressed here.
Environmental and infrastructure availability is also assumed. The data center must be built with redundant power circuits, redundant cooling and so forth so that the infrastructure remains available with single or multiple environmental faults. The data center must also be sufficiently equipped with an uninterrupted power supply (UPS) so that all hardware components can operate under brief power fluctuations. It must also be equipped with power generators to continue working during prolonged power outages.