Continuous service availability through clustered architecture
Continuous service availability through clustered architecture
With continuous service availability, instance 2 is available immediately after a failure, but most be reloaded with cache data.
Standard Memcached services are typically deployed across multiple hardware modules, but Memcached behavior is unpredictable if a module fails or some other failure occurs in the service. Instance IP addresses can vanish, triggering excessive latency or cascading failures.
Gear6 continuous service availability uses a clustering architecture that automatically fails over a failed instance to another available module. It keeps instance IP addresses alive and Memcached services functioning.
With continuous service availability, the service, but not not the cache data, is maintained in the event of a Memcached failure. This is the lowest-cost, highest-density way to deploy Gear6 Web Cache. It is suitable for applications where additional Memcached latency is acceptable after a failure has occurred, while new modules are loaded with cache data.
Gear6 Web Cache can also be configured for continuous data availability, so that normal operations continue without performance impacts throughout a failure incident. Learn more about continuous data availability.
