This is article 1 of 2 in the series “Hosting WordPress Yourself at Scale” Hosting WordPress Yourself at Scale Part 1 – Dedicated Database Server Hosting WordPress Yourself at Scale Part 2 – Network Filesystem In this series we’re going to look at how we can scale our WordPress app to handle more traffic.
In this series, we’re going to look at how we can scale our WordPress app to handle more traffic. Throughout the course of this series, we’ll build upon what we learned in Hosting WordPress Yourself and introduce more advanced concepts such as load balancing, MySQL replication and distributed filesystems. So if you haven’t yet gone through the original series, you should start there or subscribe here to get the series via email.
Unlike the original Hosting WordPress Yourself, this series will form more of a high-level overview and the step-by-step guidance will be more terse in comparison, therefore before attempting these optimizations you should have a firm grasp of the CLI and server configuration in general. Our sole aim is to increase the number of requests we can handle per second. We’re not concerned with high availability or auto scaling, although we will introduce some form of redundancy by splitting our application over multiple servers.