We will WP return data for caching, the user in the open page, directly from Node return data, WP is not involved in the implementation, coupled with Node’s natural high concurrency advantage, to achieve the click instantly open, if your server network is not too bad, the physical sense of the basic zero-latency. (At present, this demo site is not yet installed, don’t try it, we will push the update when it is installed.)
Then how to deal with dynamic data?
When the user opens the page, intelligent judgment of what dynamic data on the current page, and then asynchronously sent to the server-side processing, and return to the front-end merged data cache data, the user will almost not notice. Doing so server-side (WP) do not have to process all the data on the page once, only to deal with specific certain data, speed and efficiency are top-notch.
If WP updates the data, how is the cache handled?
If the server side (WP) has updated data, it will notify the Node side through the api interface, and the Node side will intelligently determine which caches need to be refreshed according to the data sent to it, so that the cache and server side data can be perfectly consistent.
Request a page only once
Because the content displayed on the pages of logged in users and non-logged in users are different, WP usually only caches the visitor’s page.B2 theme has solved part of the problem, and can cache the pages displayed by both visitors and logged in users, but at the cost of the user who opens the page, you need to send more than one request to the backend to get the dynamic information of logged in users. However, the cost is that after the user opens the page, it needs to send multiple requests to the backend to get the dynamic information of the logged-in user. In some cases, there may be 6 requests for a single page, so in fact, when the user opens the page once, the WP will be initialized 7 times, which is a great burden to the server when there is a heavy traffic.
With our new system, the number of requests from visitors to WP is 0, and the number of requests from logged in users to WP is 1. So this optimization is basically over.
The system has been renamed, and will use a new name and domain name in the future.
Some people said the name of our system is too random, now it has a simple and memorable name – guaqi (guaqi.com).
Guaqi is a grumpy little dinosaur, not only grumpy, but also a bit silly.
In addition, we have a multi-language function of the system, currently can support a key to intelligently translate Chinese articles into other languages, I use a free interface, the amount of small should be fine, but the use of more people, it is not possible to be limited, so you only play on the line, do not go to a large number of translated articles. The multi-language function of the plugin also has some display bugs, please ignore.
This system took a lot of thought and effort, please do not rush, interested in installing and play.
