Wordpress Scaling Infrastructure

In reference to this article:

is there a nice ‘starting’ point that I can implement which will allow the adoption of this model? For instance, can I simply start out with a web server and MariaDB server (2 servers)? Storage will be on the web server. Then, when growth is needed, separate into the file cluster model and implement another web server and load balancer?

Would this be doable or would it add a lot of complexity into things since it will require separating the storage from the web server after the fact?

Also, for SSL, I’m assuming the certificate would need to be loaded on all web servers or would the load balancer be able to handle it? Would I need a wildcard in this scenario?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This would be do-able and shouldn’t add too much complexity. As long as your web root (whether it is on the local disk or a glusterfs share should not make any difference for how WordPress itself is configured (aside from the possibility of changing the web root if your glusterfs is not mounted at /var/www/html).

For an SSL certificate you would add this to the load balancer as this is the web server that end users would interact with.