Why SQLite?
When more than one thread tries to access file read and write operation, we should handle the file lock system to avoid file and data corruption.
In order to avoid that complexity, we prefer to store the data in a database like MySQL, PostgreSQL, MongoDB (Client-Server) where data will be stored and handled by the process.
when your application does not require big Databases, but when you need CRUD functionalities in a simple file, you can prefer to use SQLite — it’s not a client-server database engine and it’s one of the most used databases.
SQLite competes with the fopen functionality and not with MYSQL, MSSQL, PostgreSQL. In most of the application’s local data storage is handled by SQLite. SQLite is an in-process library, not a server.
SQLite supports different thread modes:
https://sqlite.org/threadsafe.html
There some limitations in SQLite — not support a Boolean and not directly support the DateTime type. To know more have a look at the datatype document.
Installation and usage metrics:
SQLite author:
SQLite — Todo sample.
If you have feedback and suggestion feel free to give your comments.
