Amazon Elastic Load Balancing vs. NGINX Plus

It really is a straight-up situation. From my current experience if you have two or more services hosted on Amazon web services that need transactions between each other with a variable flow of traffic then elb is a fantastic method for routing that traffic and making sure that no one back and component gets overloaded with requests while other existing components are just standing there idle waiting for some traffic. As noted earlier in my review we are still doing a trial run with the service as not all of our components are hosted on AWS yet and we aren't having as great luck with transactions between hosted and non-hosted but that could also simply be a learning curve on our part.

Incentivized

I think that NGINX Plus could be used in place of a hardware load balancer and it would be light weight and easier to configure than a hardware based load balancer but in terms of usability a GUI for said load balancer would definitely help in setting up

Incentivized

• Good price for a complete load balancing solution
• Very useful rules editor on listener
• Working in conjuction with AWS WAF, is a good option to protect your applications

Incentivized

• Load balancing
• Caching
• App security
• Boost App performance

Incentivized

• There are not a lot of cons but we can mention the need to always check the quotas for the ELB

Incentivized

• An AI bot would be cool to help build config files
• More webinars for advanced NGINX Plus would be great
• GUI tool... might already be one available

Incentivized

No reason not to renew it, we are happy with it.

Incentivized

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

Incentivized

The UI is not there.

Incentivized

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

Incentivized

We had an issue after upgrading from RHEL 7 to 8, and there were some issues that the security team imposed upon the platform with a scanning tool. We also had a VXLAN environment that was not properly sending a gratuitous arp to the network. NGINX support was instrumental to speedily resolving our issue.

Incentivized

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.

Incentivized

Incentivized

• Allows us to troubleshoot and address network issues, which improves our end user experience
• Provides an integrated way to balance our network load without having to deal with other suites besides AWS, saving time and effort
• Allows us to see the effects that different code changes have on our network performance, which means more efficient development on the back end

Incentivized

• We are planning by using NGINX it can greatly reduce our OPEX by 50% "just our own running APIGW" the cascading effects in the long run will be much more.

Incentivized