Reachforce Case Study - Portworx


ReachForce Containerizes 200+ AWS Instances with Portworx to Reduce Data Center Footprint and CPU Utilization


  • AWS EBS storage severely under-utilized with only 25% percent of purchased capacity being used
  • At the same time, EC2 instances were over-provisioned by 100%, increasing the cost of operating the ReachForce SaaS platform
  • Data services backing the ReachForce SaaS platform must be performant, available and protected


  • Docker-based container management platform for a scalable, easy-to-use container-as-a-service offering and hosted web applications
  • Portworx Enterprise for cloud native storage and data management


Portworx aggregates all the EBS storage on the container hosts and thanks to thin provisioning, ReachForce was able to serve the same number of volumes and the same amount of data with half as much AWS storage. Containerization, including mission-critical data services, allowed ReachForce to reduce their AWS compute footprint by 50%. Because Portworx handles the connectivity between the containers and data, ReachForce’s container placement strategies can be quite simple. It is not necessary to ensure that the container is running on the same container host where the persistent volume exists in order to ensure application performance and availability.

Because Portworx aggregates all the storage on the container hosts and uses thin provisioning, we will be able to serve the same volumes and the same amount of data with half as much AWS storage. Just as importantly, though, it allows us to aggregate our storage tiers across each ECS cluster and only add more SSD or magnetic EBS storage as the data grows.”
– Tom Watson, DevOps Engineer at Reachforce