When Docker first (re) popularized the use of container-based infrastructure, there was a bit of discussion around the storage problems related to containers. Two startups came into being to try and resolve the issue: ClusterHQ and Portworx.
While ClusterHQ flamed out, Portworx is still going strong and today announced a high-profile and interesting case study.
To clarify exactly what Portworx does, users can use it to manage any database or stateful service on any infrastructure using any container scheduler, including Kubernetes, Mesosphere DC/OS and Docker Swarm. Portworx solves the five most common problems DevOps teams encounter when running containerized databases and other stateful services in production: persistence, high availability, data automation, support for multiple data stores and infrastructure, and security. As such, Portworx technology is ideally suited for solution verticals such as databases, messaging queues, continuous integration and continuous deployment (CI/CD), big data, and content management.
To read this article in full or to leave a comment, please click here
