WordPress and other popular content management systems such as Drupal and Joomla are inherently stateful, storing important data in the application itself. This makes it difficult to horizontally scale these services. With an optional NFS-based file layer, Portworx lets you horizontally scale out CMS sites while managing a single file layer. Specifically, you can run multiple WordPress, Drupal, or Joomla containers and have them access the same underlying data volume, sharing state between hosts, without worrying about users colliding on the same file.

Problems with containerizing CMSs today:

  • CMSs are inherently stateful
  • It is difficult to share a single volume between hosts

Portworx Works with Major CI/CD Platforms

Multiple CMS Containers, One Volume

Portworx supports Docker–volumes in both multi-reader and multi-writer modes. This means you can spin up multiple WordPress or other CMS containers and back them all up onto a single Docker volume. This allows you to horizontally scale your CMS without adding multiple new volumes that you will have to back up, make HA, and otherwise manage.

Ops Automation for Your CMS

In addition to providing a single volume for all your CMS containers, Portworx automates data operations with snapshots, backups and encryption and lets you manage your CMS containers from directly within your scheduler of choice, whether it’s Kubernetes, Mesos or Swarm.

Related Blog Posts

Watch Now
image
Lightboard Videos

Lightboard Sessions what are shared volumes

Architects
Architect’s Corner

Architect's Corner: How MightWeb uses containers to provide scalable websites

Architects
Architect’s Corner

Architect's Corner: Hugo Claria of Naitways talks Kubernetes storage

WordPress
How To

Kubernetes WordPress: How to Run HA WordPress on Kubernetes