You can implement RulePoint to deliver as a high-availability solution to meet your business goals. High availability eliminates single points of failure.
The run-time architecture allows you to create various high-availability designs to improve the RulePoint performance. The run-time processes continue to run despite temporary failures, and ensure minimal service interruption if a service fails.
The following interrelated features in RulePoint maintain end-to-end availability of the run-time services:
Resilience. The ability of RulePoint run time to tolerate temporary connection failures until either the resilience timeout expires or you fix the failure.
Restart and failover. The restart of a service or task after the migration of a service from a primary instance to a backup instance when the primary service instance becomes unavailable.
Recovery. The completion of run-time operations after service interruption. After a service process restarts or fails over, it restores the service state and recovers the run-time operations.
Before you begin your high-availability design, you need to understand your business requirements and which high-availability solution you need to use to solve a particular business problem. You can group the run-time components accordingly to strengthen the high availability in your environment.