The average site on a file CMS is not reasonable?

Question

CMS

There is an idea to launch a site with regular content: articles, news and special pages. The calculation is for >10,000 unique visitors per day.
Question: would it be reasonable to run a similar resource on a file CMS? Will I provide myself with a headache in a couple of months, when the number of records and pages exceeds hundreds of pieces, by choosing a NoSQL engine?
PS If everything is not as scary as I imagine, then do you have examples of such practice and experience with file CMS on medium projects?

Answer 1

IMHO I don’t recommend installing such a wordpress, my friend fell already at 6000, although a lot depends on the curvature of the hands.
I have a samopis on php that keeps 20 thousand people a day without straining with the mysql database without caching. But the selections there are not complicated, I don’t know what selections you will have, but if there are articles, news, I suppose nothing supernatural ...
If you are worried about the load on the database, I would just screw caching and get the same "file CMS"

Answer 2

By and large, the most important thing here is how often the content of the pages will change. Not just the text of the articles, but the content of the pages as a whole. If the majority of visitors will be readers, and the generated pages will be more or less static, you can do it on a file engine. Set up caching correctly and enjoy life.
But if visitors do not just read, but, say, actively comment, which means that the comment feed will be constantly updated (i.e., the final HTML pages should be updated all the time), then with good traffic this can turn out to be sad.
And here it is already necessary to install a normal engine with the base, although you should not forget about caching in this case either

Answer 3

Well... put Varnish on the front and rejoice. Wikipedia does this and rejoices.