by Aidan Clarke
In a previous article, we looked at how Brocade vADC is designed to be clustered in virtual and cloud environments. Unlike traditional HA architectures, you don't need cluster members to be Layer 2 adjacent, and nor are you restricted to simple Active/Standby configurations. In fact, there are THREE types of clustering which you might look for:
Clustering for Scale - Brocade vADC does not even limit you to two-way clustering - you can scale out to 64 nodes in a single cluster. And with each node able to drive over 140 Gbps in a single virtual instance, you have the choice to scale UP or scale OUT to suit any type of application architecture.
Clustering for Availability - Brocade vADC is not restricted to simple Active/Active and Active/Standby. You can build flexible N+M failover models, with shared or non-shared standby nodes, using Traffic IP Groups to define which services are hosted on which nodes, within a single cluster.
Clustering for Synchronization - In some architectures, you need to synchronize: each node needs to know the end points for every cluster member, so you have to replicate the configuration each time. With Brocade vADC, you define the cluster, and the configuration is replicated to all members - not just the end point IPs, but the business rules, traffic policies and access rights.
Brocade vADC excels at all three types of clustering, and there’s an extra bonus: all key capabilities such as web application security, content optimization, global load balancing and TrafficScript rules are supported and synchronized across all cluster members. Which lets you focus on what your application needs, rather than on restrictions imposed by networking and load balancing.
By contrast, traditional IT architectures meant that key capabilities were often not supported in clusters, so you might have to choose between performance, resilience and management - and lose critical capabilities.
The Brocade vADC portfolio is designed to cluster and scale horizontally - no matter what your workload, we can scale to meet it without compromising on the features offered. Configure your application once, and choose how you want the application spread across the cluster using Traffic IP Groups.
This article is part of a series, beginning with:
More to Explore: