"sfailed" - 1 õppematerjal

IT arhitektuur

Instead, each application is connected to a hub that provides connectivity between all the applications. A change or upgrade to any one application changes only its relationship with the hub and does not affect all the other applications with which it must be integrated. 29. Fault Tolerant Computing Fault Tolerant Requirements 1.Full-stateRecovery: ­In the event of a system failure, the secondary broker must be able to assume the role of it sfailed primary partner. The secondary broker must gracefully recover the full message stateprior to the failure. 2.Hot-failover: ­In the event of a system failure, the secondary broker must transition to an active state withminimum failover latency. Minimum latency ensures that client application buffers will notoverflow or applications fail. 3.ClientFailureTransparency: ­In the event of a system failure, enterprise applications must transparently fails over to the secondary messaging broker