NetScaler vs. NGINX

Citrix NetScaler is suited to any environment where hardware load-balancing, application delivery or SSL offloading is a requirement. It's a product that can be used to manipulate traffic flows in a multitude of different ways and its only limit is the protocol, application and imagination of the administrator. It's not a product that includes helpful wizards to guide the admin through each process gracefully. While it is a fairly intuitive product to use, it's not for someone who is not initiated into the ways of networking and network protocols and communication. Nor is this a product that would lend itself solely for the usage of single usage scenarios where small traffic flows would be expected (although if desired the VPX product would probably suffice in that specific scenario depending on the environment)

Incentivized

Nginx is well suited for serving any static content - whether that be images, JS files, HTML files, CSS files, videos, etc. If you have a high-traffic website, Nginx will be a great fit because it handles large number of requests extremely efficiently. Nginx has full support on Unix systems, but only has limited support on Microsoft Windows machines.

Incentivized

• The GUI interface is fairly easy to learn making ramp-up time faster than some similar products.
• It is used by thousands of companies around the globe so finding free support on Google is usually quite easy.
• The virtual implementation version of the product runs on a Linux-based hypervisor install so no additional licensing is needed for the OS.
• When used in conjunction with a Citrix Web front/Storefront, the integration is very tight making the passing of packets very quick.
• Even in the lesser VPX versions, there is the ability to have a cluster of Netscalers to allow for uptime capability.

Incentivized

• Straight-forward configuration format that users of all skill levels can learn, and yet is powerful enough for the huge breadth of features that Nginx provides.
• Massive scale right out the box. We've never had a Nginx instance overwhelmed by requests, and if we did it would be trivial to spin up more Nginx instances to handle the load.
• SSL termination means that we can deliver content over HTTPS without needing our individual services to require TLS support. This saves us a lot of time and headache while keeping us secure.
• Nginx is open-source and free, meaning that anyone can use it to power their services, from individual projects to billion-dollar websites.

Incentivized

• At times it seems like there is a flurry of firmware updates needed to remediate security vulnerabilities which creates some overhead.
• Out of the box automation using ADM is a bit lacking
• Nit picking but occasionally there are minor config changes that need to be done via CLI or GUI but nothing significant.

Incentivized

• Nginx often requires some initial configuration. It's worth doing, because you'll end up with great results, but it can be slightly daunting for someone to get started using it. Apache might have a leg up in that regard--When you install Apache, typically it's just about ready to do what you want already. But the issue with Apache is that most people skip the extensive tuning phase required after that, and with nginx it becomes more just a part of the configuration process.
• Sometimes, the configuration syntax, even though it's powerful and terse, isn't the most intuitive. Luckily there's plenty of documentation about what things mean and how to accomplish certain things. There may not be much that can be done about this--to have a powerful web server, you need a powerful-enough configuration language.
• The nginx brand is somewhat fragmented, and it can be confusing. There's the open source nginx web server, which I've primarily been referring to. But then there's NGINX Plus, a premium subscription-based service which works with a range of other NGINX products (NGINX WAF, NGINX Amplify, NGINX Controller). I've met a number of people who weren't very familiar with nginx, and instinctively went to nginx.com first, and from there it seems like everything costs money. It's only when they realize there's a different site, nginx.org, that they find what they went looking for.

Incentivized

Great value for the product

Incentivized

I gave the NetScaler a 7 here because the system once configured and deployed is very easy to use. However, if you did not deploy the system and do not have the fundamental background knowledge then you will have trouble using the product in general. Overall it is a great product and service but does typically require professional services to be deployed.

Incentivized

Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application. Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also from the administration perspective. Also, Nginx doesn't delay any request because of internal performance issues.

Incentivized

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.

Incentivized

Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.

Incentivized

Netscaler has more features than F5 BIG-IP APM product and easier to manage with friendlier user interface for network admins. It was more cost efficient as well and if you have a Citrix XenApp and XenDesktop environment, it is more compatible with those products as well. Our annual maintenance cost is lower as well.

Incentivized

I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives

Incentivized

• Features - There are many features to be used that we haven't quite gotten to.
• Licensing - The need for licensing is one of those necessary evils.
• Reporting - It gave our management team the requested graphs and statistics on usage.

Incentivized

• When we first migrated our primary bidding environment architecture to Nginx, it was under duress due to Apache's inability to keep up when we consolidated away from an HAproxy model to a central HTTP proxy. So we even when we did not know what we were doing, we were able to make it work in a bad situation, and everyone was quite happy.
• The biggest complaint I have is that I find the module compilation requirements for nginx+ rather burdensome. If we pay for Nginx+, I'd love to see then have pre-built modules for ready for each release of more modules. We are spending our own time engineering an in-house solution for module testing for nginx+ releases, which is disappointing.
• I've also, as the primary Nginx person at my organization, inserted my expertise into other projects, and have saved our company lots of money getting rid of big $$$ appliances for general SSL proxying.
• Speaking of Nginx replacing SSL appliances, we had an instance where we had to suddenly enable elliptic-curve SSL ciphers and our big $$$ appliances (you know who they are), were falling over. Even their SSL accelerator cards, after all, are just a few extra cores to process SSL. But in an environment of our size, we use DNS to spread the load to hundreds of frontend proxies with dozens of cores each to spread this load out, all at a lower price than ONE of the appliance pairs running Nginx. We couldn't even tell the change in load in our Nginx architecture when we enabled the ciphers.