I haven't worked with any other solutions similar to NetScaler in terms of load balancing, but I have experience with other firewalls for gateway and application delivery.

Previously, I used physical devices for application-related control.

I have previously used F5 BIG-IP. Citrix is more user-friendly and scalable for engineers for doing configuring. The dashboards and interface are better in Citrix ADC than F5 BIG-IP.

I found Citrix ADC the better solution.

It's not that I have used other solutions, it's just that in most environments where I have had to do my job or to come up with solutions as a solutions architect, the preferred technology was NetScaler; if not, I would suggest they use it.

However, if they had anything else, for example, F5 or A10 - if that was their preferred method - I have used those as well. So it's not up to me. But for a new customer, for a new build, my suggestion has been to go with NetScaler even if they didn't have Citrix.

The biggest misconception in the industry is that you need NetScaler if you have Citrix in your environment. And if you have any other solution, let's says VMware Horizon View, you want to use something else. But they don't realize you can use NetScaler regardless of whether you have Citrix or not.

It's not that I have switched, I have always used many different technologies, but this happens to be one of my favorites and it's one of the technologies I've been working with for a long time.

Before using Citrix NetScaler, I had experience with similar products. I recall working with Citrix Gateway for server access, but it involved a server running an application on a Windows server. I have also dabbled a bit with other vendors like F5 for feature integration. However, integrating with Citrix has been challenging as they are not very open to external integrations.

We did not previously use a different solution. 

We are also familiar with F5.

NetScaler does the same thing as an F5 and it's cheaper.

I also worked with F5. We used it for a couple of years.

Prior to this, we used the Cisco ACE solution until the product was discontinued.

I am also working with F5, Kemp, Barracuda, Cisco, and NGINX.

Loadbalancer.org is less complex than Citrix. In some cases, our customers do not have an engineer on staff who can support this device.

These customers have a large number of Linux engineers but don't have the money. We suggested using Loadbalancer.org and other open-source tools. Many customers are of different sizes and have different budgets.

Previously, I used Microsoft TMG but then switched to NetScaler since it is a better solution.

I was able to try F5 and Radware. The price for Citrix ADC here in Mexico was good when you compare it with F5 and Radware.

I've worked with F5 and found it hard to work with and manage, in comparison to Citrix.

Previously, we used Juniper VPN. The hardware was older.

I have not tried other solutions.

I have used an F5 solution. In F5, you have to do a lot of coding and scripting to be able to achieve certain things. Citrix is very straightforward because of the infrastructure that we run. It is very easy to spin up services. F5 is not straightforward.

I worked for a long time with F5. I've only worked with Microsoft and Cisco solutions. We're currently checking other options for a new customer. 

We also deal with Fortinet FortiADC, and one of our clients recently had to switch to Fortinet because of a management decision. Importantly, however, they were still happy with Citrix.

We had a mix of makes/models, as we supported a large customer base, such as F5, Cisco CSS. We have never had a case where we had to switch NetScaler out for another make.

We did not use another solution prior to this one.

I have been working with Citrix technology for the last 10 to 13 years. We have not switched solutions during this time. 

We started as a Citrix client at first. We used NetScaler in the very beginning. For a long time, we have only used this one product.

No, the whole solution is based in Citrix technology.

We deployed NSX on our infrastructure last year. It was great, except for the standard load balancer. We were already using Netscaler MPX on our physical level and expected almost the same features from NSX load balancer. But it was really hard to even monitor the services on it, and we did not have time to wait for it to be improved. So we downloaded and tested the trial version of Netscaler VPX. We've already gotten to know the product, have made comparisons with products from other brands, but it did not take long to select it. For now, it is the best solution for us.

We used Windows Network Low Balancing.

Yes, we also use F5 Big-IP LTM and in the past we used Cisco ACE. We didn’t switch specifically to use NetScaler, as we use the most appropriate solution depending on the customers needs.

We are using most of the solutions together, so there is no switching between the products. We are currently using F5, too, and we always prefer that first. But it depends on the deployment and it depends on the needs. For deployments we choose Citrix.

Prior to this solution, we used F5 BIG-IP and the Azure Load Balancer.

We previously used Kemp Load Balancer. We still have it as part of our infrastructure. The main difference between the two is the Citrix solution is part of a physical appliance, whereas the Kemp solution is a virtual appliance.

None were previously used.

Some of our clients use the F5 load balancing solution, but that is only ten to fifteen of approximately fourteen hundred clients.

NGNX, but it was not my solution.

We work with multiple ADC vendors.

No

I worked with KEMP and NetScaler.