We have customers that use it, but I'm not an administrator or operator. I just implemented it at the customer site, that's all I did.
I'm probably not as experienced as some of the customers because they use it more often than me.
Our customers use it mainly for security reasons to block access between VMs in the same subnet. Sometimes, I saw that a few of them have an isolation policy.
For example, if a VM is infected with malicious software, then they can put the category on the VM, and it goes automatically to the isolation network, which means that the VM cannot communicate with the outside. Only inside connections are possible. That's a nice feature, as well as the isolation of the Flow Network.
They are completely divided, so they can't communicate with each other. If you have a production site and, on the same cluster or in the same network, you have a test environment, you can divide them with Flow and block any communication between these two sites. That's also a nice feature in my opinion.
Nutanix Flow solution has updated the ability to control everything through API. They also introduced that they develop API first and the rest follows.
I don't use it very often because the implementation isn't huge enough to necessitate automating things. But I think it could be very solid since the API of Nutanix and the rest of the components is very good. So, I think it can be quite useful and helpful.
It has a lot of features. There is probably some confusion with the name or with the product because there is Flow micro-segmentation and also Flow networking. It's both network-related, but it's not the same product. What I know and speak about is micro-segmentation, and I think it's quite nice. It's easy, and it does what it needs to do.