Avi Networks Software Load Balancer needs to improve its documentation. If there is no documentation in Avi Networks Software Load Balancer, we need to search for a new trainer, for which we spend time searching and contacting trainers via websites.

It doesn't match the development structure or user community of our existing product. It pales in comparison to that.

It's not fully grown up. Other people might think that, however, our comparison against a product line that we use shows it's not as grown up as the existing product line.

We'd like it to be more open to third-party integration.

Their salespeople can be a bit aggressive. They're trying to get into an area that is dominated by large vendors elsewhere. So they tend to be a little bit more aggressive than some people would like.

I'm not sure if there is a particular area that needs improvement. 

The initial setup is a bit complex. 

The network analytics and monitoring features are not effective. The product does not provide deep troubleshooting features. The solution must provide public IP features. F5 provides such features.

One struggle with Avi Networks Software Load Balancer is its integration with other VMware products. Integration could be improved in the solution so that you have a more unified control plane with it and other data center security and networking products that VMware sells. There has been a bit of a lag on the roadmap of new features that have come out there recently, but better interoperability with the hyperscale environments such as the AWS, Azure, GCPs of the world, and simpler deployment and interoperability with those existing tools, are areas that are receiving attention and could use additional attention today. These are the areas for improvement in Avi Networks Software Load Balancer.

What I'd like to see in the next release of the product is further extension into service-managed capabilities, particularly for Kubernetes environments. That's going to be a big player.

Some pretty cutting-edge API security capabilities are being built into Avi Networks Software Load Balancer that are covering big tag vectors that people will continue to see when scaling out microservices applications. Those are also going to be big players moving forward and differentiators for the platform.

The product could be improved in terms of security features. For example, IDS and IPS sites need to be more progressive.

I really liked Avi Networks, but we are looking for more secure stuff. After downloading the report from IT Central Station, I spoke to the account manager of Avi Networks in the Middle East, and he said that they are selling the module we need as a separate product. I didn't want it because I don't want to have product upon product for each and every functionality.

I work for a major municipality and the whole our infrastructure runs on F5. We have close to eight F5s, the bigger boxes. F5 has a product called APM and that is not in the box with Avi Networks; you need to buy another product. I wish they included everything in one box because that's how we buy a product, especially an application load balancer. 

Everybody has to compete with the market leader and F5 is the market leader. But F5 is very expensive and that's why everybody wants to go to the cheaper load balancers. But to do that the competition has to include all the functionalities of F5. Avi Networks is great. It could be good for a small company, but for the whole municipality, it's just not good enough.

Avi Networks could put all the modules of F5, which are available in their hardware box, inside the software. They shouldn't sell the products separately. I would say 90 percent of the people in the Middle won't buy it. I know the government sector, and they wouldn't buy it.

For example, if you have a washing and the dryer comes separately, you're not going to buy it. The washing machine is great. It does great washing, but you have to buy another apparatus for drying. That just wouldn't work. With Avi Networks you have to accommodate the extra product in the data center. Of course, they say that they are all virtual, all software-based, but there is still a lot of software integrations and connectivity that are required.

Avi Networks is something I really wanted to go with and try because our F5 is a million-dollar-plus contract. Two of our F5s are going out of support, end-of-life. I really thought we could change it but for now, we cannot. If Avi Networks could bundle everything as one...

In terms of improvement, the pricing and documentation need improvement. We have had problems getting the documents.