| < Previous page | Next page > |
Mirror Cache
Mirror cache consists of two server active/passive nodes. One server node is active node which is basically the coordinator node . The coordinator node is the oldest server node in any cache cluster having membership management
authorities. The other node is passive/mirror node.
Clients Connection: All cache client can only connect with the active node. Passive node is added for creating the exact backup of active node.
Backup Support: Mirror cache provides data reliability by creating a backup through asynchronous replication of all updates on mirror/passive node. Due to asynchronous replication between active and passive node, cache clients get
better performance. Active and passive servers can be interchanged at any time.
Failure Recovery: If active node goes down due to any reason, then passive node automatically becomes active without any intervention. All the cache clients connect to the new active node and can perform operations without any
performance degradation and downtime.
Runtime Scalability: As there is a single active node in this topology, its scalability is the same as that of a local
cache. But due to mirroring of data, it also provides fault tolerance which lacks in local cache.
State Transfer: Mirror node always replicates the state from active node when it joins the cache cluster.
See Also
|