1. Introduction I've been using a base-level VPS (US$39/year) from Racknerd's Chicago data center to build the "read-only node" in my blog's active-active architecture for about half a year now. Over this time, the VPS's overall stability has been quite good…
1. Introduction Since building my blog with WordPress, WordPress's inherent mechanism of allowing only one URL for access has been a source of much frustration for me. The reason is simple—when accessing the admin panel, I also have to use the domain name. And accessing the admin panel via domain name inevitably…
1. The WordPress Caching Dilemma and Solutions 1.1 Why Do Many WordPress Site Owners Prefer to Give Up CDN? In the world of static sites, CDN is almost a "free performance optimization": static files are naturally suitable for caching, and HTML pages are almost...
1 Introduction In my previous multi-active architecture deployment practice (see: Home Data Center Series WordPress Multi-Active Architecture (Simplified Version) Implementation Plan in Personal Blog), Cloudflare's health checks are the key to achieving node...
1 Introduction In the previous article (see: Home Data Center Series WordPress website uses Simply Static plugin to achieve site static), I introduced in detail how to use Simply Static on WordPress…
1 Background Introduction The original idea of developing a WordPress multi-active solution was actually very simple: the Internet at home was cut off by the telecommunications company for three days without any warning (see the article: Home Data Center Series From this time when the Internet was cut off at home, I talked about my current personal blog…
1 Introduction Since my blog uses a special WordPress active-active architecture (the macmini in the home data center is the primary write and secondary read node, and the VPS in Chicago Racknerd is the primary read node), once the macmini node has content changes (all blogs…
1 Introduction When deploying a WordPress multi-active node solution, a crucial technical point is read-write separation: that is, all operations involving "writing to the database" (such as publishing articles, modifying content, modifying plugin configuration, submitting comments, etc.) are uniformly routed to the primary write node for completion, while other nodes...
1 Introduction I have always wanted to build a synchronously updated static copy for a dynamic blog based on WordPress. On the one hand, it is out of the pursuit of "full site cache" and "always online" capabilities - after all, early blogs have not yet achieved disaster recovery and dual-active deployment, and WordPress itself...
1 Introduction My previous blog architecture is a home data center (master node + hot standby node) + Tencent Cloud (disaster recovery node), which is a typical "single node read and write" solution. Since only the master node is responsible for processing database read and write requests on a daily basis, there is no need for real-time synchronization between databases: every time...