Amazon's Elastic Load Balancing automatically distributes incoming application traffic across multiple targets, such as Amazon EC2 instances, containers, IP addresses, and Lambda functions. It can handle the varying load of your application traffic in a single Availability Zone or across multiple Availability Zones. Elastic Load Balancing offers three types of load balancers with the vendor states all feature the high availability, automatic scaling, and robust security necessary to make…
$0.01
Partial Hour
NetScaler ADC
Score 8.1 out of 10
N/A
NetScaler ADC is an application delivery controller.
We use Amazon Elastic Load Balancers to serve mobile applications and websites. It works really well. We have not had any problems until now. Last year we integrated the AWS ELB with the EC2 Auto Scaling and now we have a fully working elastic solution. We increase/decrease EC2s instances based on traffic over our load balancers.
Citrix Netscaler can be a powerful network appliance for environments that are fully committed and open to utilizing a network appliance that isn't made by a traditional network vendor. Administrator user experience has improved over the years and will continue to improve with the flexibility of virtual and physical appliances available for medium and large enterprises.
Flexibility. NetScaler assumes its admins know a bit about networking and in-depth details surrounding the applications they are configuring access for/to. This being so, the range of configuration options is very broad allowing various versions' combinations of protocol patterns, expressions, rules etc., all to the benefit of the admin.
Granularity. Having such a broad range of configuration options available, while still allowing simple options to be configured simply. The GUI is well-stylized and navigation has a good flow.
Ease of control. For load-balancing of simple services right out of the box, NetScaler makes it pretty easy, compared to the range of options available in the surrounding GUI and under the hood.
Occasionally we have a huge number of users using our network at once, and Amazon ELB isn't quite fast enough to scale effectively when that occurs. But this doesn't happen very often as our usage is usually quite stable
If we want to add another application to our learning suite, we would have to add another load balancer, which would incur additional cost
The setup was not easy and could really only be handled by one person on our team with the technical background to do so
The documentation could use an overhaul with specific examples related to the command line as well as GUI. Explanations in the documentation would also be helpful.
Being able to have more than just one routing table would allow the ability to leverage security.
AWS Elastic Load Balancing has this trick. First, you need to know how it works. ELB is not the only piece here. ELB has a very close relation with AWS Target Groups. You create or select a target group every time you create a Load balancer. Target groups allow you to connect the load balancer to EC2 autoscaling groups, Lambda functions, or even a single EC2 instance. While this sounds complex, it becomes easy, once you know his tricks. Thanks to the user interface, managing a ELB is an easy task. The rules editor is really useful, although it will need a bit of improvement to some interface items
Improve on the specifics I mentioned previously and could be a 10/10 product. It is also a confusingly branded product that I have supported in two large enterprises where IT departments are unsure if the product belongs to the Citrix remote access support team or the Network infrastructure support team (it should be the later) and typically under utilized.
AWS gives you several support plans. On the free plan, you basicaly need to google for help, but the good news is that AWS Elastic Load Balancing works. We has more than 15 load balancers and we never run into a problem that require support. But you mght consider a support plan if you are going to do something more complex or critical
Overall, our organization's experience with Citrix support is that support can be hit or miss. Oftentimes it takes multiple attempts and much longer than desirable to obtain a viable solution for issues experienced with their products. It would be great to see Citrix invest time, effort, and almighty dollars into improving their support and bug fix process across the board.
We have not used any other solution out there in the market but our dev-ops team did deep research and AWS provided us the solution we needed to be cost-effective. Also, the decision to keep working with Amazon was strategic. We were already using other AWS features and [Amazon Elastic Load Balancing] integrates great with those.
We chose Citrix ADC over Kemp and F5 due to additional integrations with various products such as Citrix/Horizon/Monitoring tools. We additionally chose ADC due to better ease of use and ability to have the appliances be virtual or physical, with the configuration being a simple migration of code which provided flexibility to be able to do a hybrid environment with ease.
