Share your experience using Venusense ADC

We use several Amazon solutions including Lambda, S3, and EKS. Within EKS, there are various microservices, and DynamoDB is one of them in terms of databases. We also use various applications such as Java, Tomcat, and others.

For my use case with Amazon, S3 is primarily used for file services and storage, along with Kubernetes. I am not using other solutions from Amazon directly, such as Snowball or SimpleDB.

I am using Elastic File Store for Amazon File Services, which is the full name of the Elastic File System we are working with.

I have been working with Amazon Elastic Load Balancing for more than three years for various applications and moving on from F5. We use Amazon Elastic Load Balancing with AWS FSx, a file service from NetApp.

When there is high load and an auto-scaling group is attached, Amazon Elastic Load Balancing provides assistance. It provides content-based routing features of the application load balancer, though this adds to cost, so we have those only for critical apps.

I utilize the Network Load Balancer, which we still have on-premises. The Network Load Balancer is helpful for performance enhancement and availability. Amazon Elastic Load Balancing offers flexibility as it can be accessed from various regions and zones.

Availability is one of the main benefits that Amazon Elastic Load Balancing provides to my company. For any critical application that needs to be available, we use it primarily for availability. Amazon Elastic Load Balancing helps during peak traffic times by using round-robin ordering to move traffic.

Cost is definitely an area of improvement for Amazon.

Availability can be improved through the addition of more regions. For example, in India, we have just two regions at the moment, which impacts latency. Having more regions would reduce latency.

Quality is another aspect that can be improved.

I have been working with this product for less than a year.

The stability for Amazon Elastic Load Balancing rates as a 10.

The scalability, ability to scale, and ability to expand rate as a nine.

Based on my experience, Amazon technical support rates as a seven.

Positive

The initial setup for Amazon Elastic Load Balancing is very straightforward.

Google Cloud Platform (GCP) is superior for load balancing in terms of both cost and functionality. If given the choice, I would choose Google for load balancing.

I would prefer to remain totally anonymous. I am a partner with Amazon. I rate this solution as 8 out of 10.

I have been using Microsoft Azure Application Gateway for a period of more than 10 years, but not in one application. I am a solution architect and I recommend API gateway to use in customer products.

We are partners because we work as solution providers to customers. As part of that, we recommend solutions.

My clients are all big customers across the globe, basically financial services clients.

The best features for Microsoft Azure Application Gateway basically protect your application and provide security-related features and also divert the traffic to different instances of your application.

I have used URL-based routing, which helps manage traffic efficiency. It is a bit hard to manage in the long run, but it does provide value.

I have used the gateway's Web Application Firewall feature, which enhances security as it is the first entry point to your network from the outside world. It helps protect against unwanted requests and other threats that can be configured.

Regarding the integration with Azure Active Directory, it helps with authentication processes to configure all the users or the groups.

The monitoring capabilities on Azure provide insight into application performance and potential threats because monitoring comes with many products. On Azure, you have Azure Monitor itself to help you monitor the application by collecting data. You have Application Insights and the logging workspace on Azure. By combining these three, you can implement monitoring solutions on Azure applications.

Auto-scaling is important because it helps in resource management for customers. Scaling is one of the key features of moving to cloud for any customer. During peak times or special events, such as retail site promotions, user load increases significantly. To address this, based on the number of incoming requests or server capacities such as CPU and memory, you can automatically identify these peak scenarios and configure either scaling up or down automatically based on certain parameters.

Microsoft Azure Application Gateway has room for improvement because it offers many features, but its configuration is a bit difficult, at least from the developer point of view.

There are multiple scenarios in which you can configure a product as an entry point. There is another gateway, APIM, which also acts as an entry point to protect your APIs in special scenarios.

I have been using Microsoft Azure Application Gateway for a period of more than 10 years.

The deployment can be easy if you follow automation infrastructure as code, but if you do it manually, then it becomes challenging.

The stability is good, and except for a few instances, I don't see the non-availability of Azure Cloud services.

Microsoft Azure Application Gateway is a scalable solution, and from my experience, I would rate it as nine out of ten.

I would rate Microsoft support as good because they have a very skilled technical support team in the background and usually respond in one to two days, depending on the ticket priority based on the SLA. I have experienced very good support.

Positive

Regarding the pricing for Microsoft Azure Application Gateway, I cannot provide details as I am not aware of the current pricing structure.

I would recommend this product to other users based on the need because it helps to divert or route the traffic and also provides security. If those are the scenarios, I definitely would recommend.

On a scale of 1-10, I rate Microsoft Azure Application Gateway a 9 overall.