NetScaler multi-tenancy shootout: SDX against Trafficking Areas

2:34 PM
NetScaler multi-tenancy shootout: SDX against Trafficking Areas -

NetScaler was the first to provide support for true multi-tenant environments. I am not speaking of some rudimentary administration approach of using Role Based (RBA). Rather full scale total isolation for up to forty power packed independent instances running on SDX appliances. To date, no alternative provider has this capability with a complete separation of computation, memory, hardware SSL supported and I / O without limits on the simultaneous use of the module. But the thought did not occur to me that not every one of you needs Tesla S with a performance option when a good old Volt will do the job. This also applies to the application delivery controllers (ADC). So who should rev with SDX and when did you tone it down with NetScaler with the fields of circulation ?

The table below shows how SDX is still the king of full multi-tenant ADCs able. Enterprise IT organizations of all kinds generally require strong isolation provided by SDX. Specifically, version independence, and high availability required to support the various life cycle needs of different groups of applications. In addition, they appreciate the isolation of strong resources, especially if they want to put different instances in different security zones. Although some of these operations may choose to start with the areas of movement (and this may be sufficient for the short term) all NetScaler MPX appliances with areas of movement can be converted into a SDX model on site if needed ; and probably take a lot less time than charging an electric vehicle with a 240V / 40A outlet. Yet even if the areas of movement are not for everyone, they have their place.

Service Providers with MS management

In this deployment areas of movement the NetScaler option with their procedures simpler configuration can make the most sense. The ability to segment and isolate network traffic with the duplicate IP support enables the service provider to turn virtual IP for each tenant. All the time not having to worry about whether the private IP space a tenant will conflict with another. In general, lack of RBA and isolation configuration with the areas of traffic is not a problem, as the service provider itself is service management. In most cases, the service is exposed through the supplier portal. The supplier will use the NetScaler Nitro API to automate the creation of VIP and expose the algorithm selection and the creation of services via its portal.

Service Providers with environments "commodity"

areas of movement can be a viable solution for service providers who need to deliver commoditized , "Layer 4 load balancing-as-a-service". These plans are generally known as a model "VIP by tenant" and in this situation, the service provider also provides support management. Customers are usually small and do not require their own instance.

Service providers with the application level support tenants or managed networks

For service providers offering great value deals -add or allowing customers to manage the network, I suggest you stick with SDX. These NetScaler appliances enable end users to leverage the high value of layer 7 NetScaler capabilities and give each tenant their own dedicated instance. The high insulation prevents overtaking "noisy neighbors". HA version and independence is essential to meet the expectations of service levels around change management. Most of these clients, usually larger, also place great value in having their own dedicated instance as well.

SDX and Traffic Domains not mutually exclusive

Many providers services and certain business operations will actually need both. NetScaler SDX instances (or VPX virtual appliances) provide forums dedicated to high value / large customers. At the same time, the areas of traffic NetScaler (either on or in MPX SDX instance) provide a good, L4 load balancing-as-a-service offering. Service providers benefit by making the most efficient use of available network infrastructure while providing fully private networks by tenant. End customers are happy because they can determine their own private IP address spaces in both cases.

So there you go, deploy both. And while you're buying a Tesla for long trips in the country and a Volt for commuting. And double your $ 7,500 federal tax credit! No, I do not MOONLIGHT as new car dealers.

Previous
Next Post »
0 Komentar