50% of referral website visitors initially use the menu.
There is a common view amongst local web designers & web developers that, by default, a site's data should be saved in a full-blown Relational Database Management System like MySQL or PostgreSQL. I am deliberately ignoring simple HTML pages for this post. Perhaps, because WordPress & Joomla are the go-to choices of CMS for most. But is MySQL the only storage option best suited for every website? Not at all. Let's see the factors that make a fully blown RDBMS an overkill for your little website:
So what should you use if you do not want to handle all this complexity? Not files since you do not want to push around files or run fopen() operations everytime. Enter SQLite. SQLite can offer all the advantages plus much more. And it is faster than normal fopen() file operations. SQLite saves everything in a database file. All it's operations follow SQL standards - SQL queries and all. Everything is so darn simple with it. No need to worry about database downtimes or latency problems through the network.
However, if your site will handle many concurrent users updating the site, is a high traffic site, or you foresee hitting greater than 140TB of data in the near future, or one where you want to separate the database from your application's server then SQLite is not for you.