My organization has been using Portworx Enterprise for the last two years across a couple of projects. We deploy Portworx Enterprise as a cloud-native storage solution on top of Kubernetes. We have several workloads running on Kubernetes, including application services that are both stateless and stateful. For those applications, we provide storage from Portworx Enterprise. We have Portworx Enterprise deployed in one of our projects on a Kubernetes cluster running on-premises. We consume Portworx Enterprise for our applications using persistent volumes and persistent volume claims. It provides high availability with good backup and disaster recovery solutions, and it is designed for a cloud-native environment, which outlines how we are using it. One specific example of Portworx Enterprise making a difference in my organization is with an application that stores configuration and data. To store that data, we need persistent volumes for our applications, which the application team requested, and we provide persistent volumes coming from Portworx Enterprise. We also provide storage from Portworx Enterprise for our monitoring solution, logging stack, and internal container registry hosted on our on-premises Kubernetes environment.
In the case of Portworx Enterprise, we have been developing our first couple of projects, and I find it to be a strong option on the market. We have known Kubernetes for a long time and have been working with those kinds of environments for modern applications. The satisfaction is quite high. The features we are finding have no doubt delivered what was promised. I can only compare it with Trident from NetApp, so I do not have all the information to tell you this is the best solution, but we are very satisfied with Portworx Enterprise.
The primary and exclusive purpose of this software is dedicated to storage, specifically for provisioning pure volumes within containerized environments.
The main purpose was to replace the NSS as the back-end storage because they were using open source products. We shifted to Portworx to mainly implement shared volumes. We do not use the solution in a heavy environment.
Database Infrastructure Engineer at a computer software company with 1,001-5,000 employees
Real User
May 10, 2023
We use it for storage. In terms of data locality, Portworx is pretty good compared to other technologies in the long run. We also have other SBS layers, but those are not enterprise, and there are not many offerings from those technologies, so I understand.
Portworx Enterprise specializes in security, backup, and disaster recovery for Kubernetes. It offers advanced multi-cluster storage management, enabling seamless migration between on-premises and cloud environments.Portworx Enterprise provides robust security and management features essential for Kubernetes environments, supporting efficient cross-cluster storage management and facilitating smooth migration between on-premises and cloud platforms. Its resilience and functionality allow users...
My organization has been using Portworx Enterprise for the last two years across a couple of projects. We deploy Portworx Enterprise as a cloud-native storage solution on top of Kubernetes. We have several workloads running on Kubernetes, including application services that are both stateless and stateful. For those applications, we provide storage from Portworx Enterprise. We have Portworx Enterprise deployed in one of our projects on a Kubernetes cluster running on-premises. We consume Portworx Enterprise for our applications using persistent volumes and persistent volume claims. It provides high availability with good backup and disaster recovery solutions, and it is designed for a cloud-native environment, which outlines how we are using it. One specific example of Portworx Enterprise making a difference in my organization is with an application that stores configuration and data. To store that data, we need persistent volumes for our applications, which the application team requested, and we provide persistent volumes coming from Portworx Enterprise. We also provide storage from Portworx Enterprise for our monitoring solution, logging stack, and internal container registry hosted on our on-premises Kubernetes environment.
In the case of Portworx Enterprise, we have been developing our first couple of projects, and I find it to be a strong option on the market. We have known Kubernetes for a long time and have been working with those kinds of environments for modern applications. The satisfaction is quite high. The features we are finding have no doubt delivered what was promised. I can only compare it with Trident from NetApp, so I do not have all the information to tell you this is the best solution, but we are very satisfied with Portworx Enterprise.
The primary and exclusive purpose of this software is dedicated to storage, specifically for provisioning pure volumes within containerized environments.
The main purpose was to replace the NSS as the back-end storage because they were using open source products. We shifted to Portworx to mainly implement shared volumes. We do not use the solution in a heavy environment.
We use it for storage. In terms of data locality, Portworx is pretty good compared to other technologies in the long run. We also have other SBS layers, but those are not enterprise, and there are not many offerings from those technologies, so I understand.
Portworx Enterprise is really useful when we are working in a cloud environment or when we are working with Kubernetes.
We don't have much experience with Portworx, but it's primarily for containers.