Using SQLite databases is the best choice for CMS for Small and Medium sites

SQLite is a lightweight database system similar to access, but it is smaller, faster, with larger capacity and higher concurrency.

Why is SQLite most suitable for CMS? It doesn't mean that other databases are not good. Oracle, MySQL, and sqlserver are also excellent DBS, but they have different design objectives and features. Therefore, they are only applicable to a specific application scenario, there is no absolute difference between good and bad.

The CMS features of small and medium sites I have summarized are as follows:
1. The data volume cannot exceed 0.1 million
2. The page traffic does not exceed 0.1 million
3. Some websites generate all static pages, and some websites query the database for dynamic access in real time.
4 webmasters do not understand technology or complex database maintenance. They only use ftp to manage websites.
Five personal sites are basically managed by one person. Generally, only one person accesses the background without concurrency.
6. For the database, it is read-write-less. It is written only when the webmaster accesses the background.
More than 7 running on Virtual Hosts. Most PHP hosts support MySQL at the same time. A small number of PHP hosts need to purchase MySQL separately. The price of PHP + MySQL hosts is higher than that of PHP hosts.
(Take hichina For example: the cheapest PHP space is 780 yuan, and the cheapest PHP + MySQL PHP space is 1150 yuan)
8. The HTTP service and MySQL of most small and medium sites are deployed on the same server.

The advantages of SQLite are highlighted in the CMS application scenarios of Small and Medium-sized websites:
It is more free than MySQL, and has no restrictions on usage.
Very small. PhP5 and later versions support SQLite without any configuration.
No need to separately purchase database services, no server processes, Zero Configuration cost
The entire database is stored in a single file. Data Import, export, backup, and recovery are all copy files, and maintenance difficulty is zero.
Fast Reading Speed: the speed is faster when the data volume is not large. More importantly, the database remote connection is saved.
Without complex permission verification, you can open it and perform operations.

The disadvantages of SQLite are circumvented in the CMS application scenarios of Small and Medium websites:
Low concurrency. When the access volume does not exceed 0.1 million PV during dynamic access, SQLite has more than enough concurrent access capability. After generating static pages, you do not need to consider database concurrency issues.
In the case of large data volumes, the performance is poor, but the data volume of small and medium-sized sites generally does not exceed 0.1 million, while SQLite does well under 1 million data volumes, because the remote connection to the database server is saved, it may be faster.
The write speed is slow. The write speed of SQLite in the default configuration is much slower than that of MySQL, but the write operations in CMS application scenarios are less. Insert newArticleWhen you do not feel slow. Concentrated database write operations only appear during installation, but only once, can be ignored
Adding an index to an existing table is slow, but this requirement does not exist in the CMS of Small and Medium sites.
MySQL cannot be deployed on different servers than the front-end server, but small and medium sites do not need to be deployed separately.

To sum up, SQLite can minimize the site construction cost, reduce the maintenance difficulty, and avoid its own shortcomings in the application scenarios of CMS for Small and Medium sites. So I think the CMS system supporting SQLite will surely become popular in the future.