5 Secrets of Highly-Available Integration Infrastructure 
Progress Software describes five misconceptions or "dirty little secrets' about high availability for IT integration infrastructure. The report discusses failover clusters and says five-nines uptime may not reflect true business costs of failures.
Progress Software describes five misconceptions or "dirty little secrets' about high availability for IT integration infrastructure. The report discusses failover clusters and says five-nines uptime may not reflect true business costs of failures.
Most integration infrastructure use clustering to achieve high-availability, recover from failure and restore services, according to Hub Vandervoort, CTO of Progress Software's SOA Infrastructure. "However, the bad news is that there is often a gap between what the business expects and what this infrastructure actually delivers."
Rather than measure high-availability in uptime, Vandervoort suggested it should be measured in terms of 'recovery time.' The rational is simple, Vandervoort said: Put simple, customers care about how long their systems will be unable to process transactions during a failure.
According to Progress Software, the five dirty little secrets of highly available integration infrastructure are:
In summary, the Progress report concludes high availability through clustering doesn't deliver what business managers are looking for - always on availability
"Unless an integration infrastructure provides 'continuous availability'—meaning that transaction processing continues uninterrupted despite system failure—infrastructure called 'highly available' is actually only 'mostly available,' Vandervoort said.
