You can use a feed table and a feeditem table to sort data by time. However, zhihu homepage 1. Displays content based on the following tags. 2. The content is sorted by weight. If mysql is used, I/O is too frequent because of frequent changes in likes and replies. If redis is used... you can use a feed table and a feeditem table to sort data by time. However, zhihu homepage 1. Displays content based on the following tags. 2. The content is sorted by weight.
If mysql is used, I/O is too frequent because of frequent changes in the like and reply actions. If redis is used, the content under a tag is stored in an ordered collection, you can think of a tag set as a black box, so that the user does not need to retrieve all data based on the tag to perform a total sorting. How does one implement it?
Reply content:
You can use a feed table and a feeditem table to sort data by time. However, zhihu homepage 1. Displays content based on the following tags. 2. The content is sorted by weight.
If mysql is used, I/O is too frequent because of frequent changes in the like and reply actions. If redis is used, the content under a tag is stored in an ordered collection, you can think of a tag set as a black box, so that the user does not need to retrieve all data based on the tag to perform a total sorting. How does one implement it?
I don't think it is so complicated. This is not a sort process but a push process.
Previously, it was pushed by time, and now it is pushed by importance