Skip to content

stateful or stateless, whats the best approach? #50

Description

@bennibu

I am evaluating the deployment of wordpress with docker for high availability and the biggest issue I found so far is wordpress need for a persisted file system (for uploads/themes etc). This is not particularly docker related, but as docker containers are ephemeral, there should be some tips and tricks to work around this.

So far, I have seen two approaches, a stateful and stateless one. As the stateless version fits better to the docker principles, you have to tweak wordpress very much and the configuration is not very comfortable. The stateful version doesn't need modifications to wordpress but have deal with a distributed filesystem.

At the moment, I would start with the stateless approach, because running distributed filesystems in a docker cluster doesn't seem to be an easy task.

I appreciate any ideas, experiences to this topic. Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions