There is a strange dilemma in the implementation of the review on the website.
It is expected that there will be a large number of articles (actually not articles, but that's not the point) and the actual (frequently requested) only a small part of them, with a small period of time actual move these to the archive (without possibility of adding new comments). How to organize storage in a relational database for all the review, taking into account that the main indicator is the speed of processing/delivery?
Actually while thinking about two options:
— General table of comments (confused by the possible speed reduction issue in the growth process of the table)
— A separate table for each article
Allow the possibility that I do not look at that angle on the case.