This is article 2 of 2 in the series “Hosting WordPress Yourself at Scale” Hosting WordPress Yourself at Scale Part 2 – Network Filesystem In the first post of this series, we started scaling our WordPress app to handle more traffic by extracting the database to a separate server so that we can eventually add multiple app servers to our infrastructure. In this post we’re going to do the same for the filesystem and also introduce a level of high-availability and high-reliability by building a replicated network filesystem using Gluster. But, before we start building a network filesystem it’s important to know why we need to do so in the first place. Reminder that in this series, we’re building upon what we learned in our original Hosting WordPress Yourself series. So if you haven’t yet gone through the original, you should start there or subscribe here to get the series via email. Why a Network Filesystem? Let’s say a user uploads an image to the WordPress Media Library and embeds it into a blog post. Once published, traffic to the post will be distributed to the app servers via our load balancer (which we’ll be adding in the next
Share This