Amazon Elastic Load Balancing vs. NGINX Plus

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.

Incentivized

Makes our life easy as application admins in securing our applications and making them accessible. We can easily add an application within a few minutes and define the backend servers right away.

Incentivized

• Most obviously it works great for routing traffic between components hosted on Amazon web services
• The ability to dynamically spin up connections is fantastic.
• In general the ease of use and configuration is a selling point.

Incentivized

• APIGW
• Policy Enforcement
• Centrally Manage API Traffic

Incentivized

• 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

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

Very easy to use

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

The API and dashboard alone make NGINX Plus a better choice.

Incentivized

• Currently it is too soon to say for sure what kind of impact this will have.
• The ideal goal is that this will be cheaper than having to host our own routing on site.

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