What is most valuable?
The ability to scale from different clouds. At the moment, the scalability of the product is the number one thing that I saw.
Right now, we're doing a private cloud, since we're government. In the future, we may want to look at public, but probably not.
How has it helped my organization?
It has the potential to improve the way we function by having our different clouds be able to easily communicate back and forth. Right now, it takes a lot of work to do collaboration from our test lab, to our production, and to do anything in-between. It has the potential of giving us streamline migrations from the test lab to production.
What needs improvement?
Pricing and licensing could be improved as we are a government entity. Lower pricing could always help.
For how long have I used the solution?
Buyer's Guide
VMware NSX
February 2025
Learn what your peers think about VMware NSX. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
841,152 professionals have used our research since 2012.
What was my experience with deployment of the solution?
About five to 10 people set new products up and we kick them down the road all the time. As soon as we see something real good we call in some users and it gets big. They call their managers and it grows; it's like a wildfire.
But it will start off as a spark, and I'm the spark.
What do I think about the stability of the solution?
It is pretty good. It cuts down on duplication. Right now, I have tools in the lab, have tools in pre-prod, and have tools in production.
Right now and well in the future, if we implement it, we'll be able to have the same tool set be applied through all regions and transfer and not have duplication. It will outline and teach our users how to operate them. Therefore, we will have one set of tools, one set of instructions, and they can operate in all three environments.
What do I think about the scalability of the solution?
Scalability definitely looks awesome. Again the three environments we'll be able to use one set of tools. Everybody would be familiar with it. It won't operate this region and a different way in another region because it's from another vendor, where one set of tools would be able to pass throughout all of our regions.
Our scale right now is about 60 users (the production and the customer).
Which solution did I use previously and why did I switch?
We had multiple solutions.
We were making do with what we had, but again, going to different conferences and seeing what other people were using. We got curious and our vendor said, let's demo it. So, we made time for it, and after we made time for the demo, we realized we should have been doing this two years ago.
How was the initial setup?
I was involved in the initial setup. It was straightforward. We did it with our government PFE.
What about the implementation team?
We do have partners, who are knowledgeable, did offer to come in and set it up for us. We had access to our online lab from our vendor, so they had to set it up, connect it, demo it, and see how it runs. Though, we set ours up.
Which other solutions did I evaluate?
What other advice do I have?
It's a solid product. Very easy to use out-of-the-box. It didn't have a steep learning curve, and we're still finding things that we can add-on.
I would encourage anyone looking to buy the solution to demo it in a lab, or come to a conference and see it. They should see how it would fit in their environment, and don't be overwhelmed or overworked by adding another solution because the results pays off.
Most important criteria when selecting a vendor:
- Price
- Security
- Meeting the application requirements.
- Technical support.
Disclosure: I am a real user, and this review is based on my own experience and opinions.