Degree of files, not database
Some CMSs do not use a database to store articles, but conventional text files. It would be interesting to know what problems might arise in that case with a large number of articles.
So far, the only thing that comes to mind is searching, but if you want it, can be accelerated if you create an index.
PS. I've been enjoying myself for a long time, but the articles are not much at this point.
- Backup. We'll have to copy the files separately from the base. If It's a time of trespassing, so the files may not be a little bit. synchronized with base.
- Indication. Many bases support full-text search and appropriate indices. In their fields, they're looking for and They're indexing, and there are external files - who knows? Of course. Do the field specifically for the index storage (single from text) Remove key words and put them in this field.
- Switching from one method of receiving/recording data to another. That's it. It's just inconvenience. In some cases it will be. use not habitual SELECT/INSERT, but more effective on large-scale database sweating interfaces)
In any case, additional efforts have to be made to synchronize OBD and external records. Where this is really important, databases and file systems need to be used to support distributed transactions, to coordinate bd transactions and fs.