When comparing SQLite vs Redis, the Slant community recommends Redis for most people. In the question“What are the best databases to use for Node.js applications?” Redis is ranked 4th while SQLite is ranked 7th.
Ranked in these QuestionsQuestion Ranking
Pro Great language support
SQLite is also only 350KiB in size.
An SQLite database is a single ordinary disk file that can be located anywhere in the directory hierarchy. It works by sending requests to a single file where all the data is kept instead of communicating with a hosted database which gives access to an interface by making use of sockets and ports. The file format used is also cross-platform, so can easily be migrated to various machines.
This makes SQLite extremely portable throughout different applications, all that's needed to transfer the whole database is to make a copy of the file.
Pro Not unnecessarily fiddly
SQLite is largely self-contained. It requires very minimal support from external libraries or from the operating system.
Pro Great for testing and first stages of development
Because of it's ability to scale and with the portability that a single-file database gives you without losing much of the power and features that SQL gives developers, it's a great choice for testing applications and for the early stages of development when the workload and the data that needs to be stored is not that large.
Pro Zero configuration
There is literally no configuration required to get SQL lite up and running. This is mainly due to SQLite being serverless, there is no separate server process to install, setup, configure, initialize, manage, and troubleshoot.
With less complication, there is less to go wrong.
Pro Redis is written in ANSI C and therefore doesn't have a VM
Pro Good support
Redis has great docs, an active mailing list, and a github community.
Pro Redis uses the BSD license
This means that it is able to be used in a commercial product if one wants.
Pro There are numerous client libraries and frameworks to make redis more powerful
For Node.JS for example you can get something similar to what Parse.com was offering by using Node ORM.
Con No multi user
Lacks multi-user capabilities, see SQLite vs. MySQL vs. PostgreSQL: A Comparison of Relational Databases.
Also see: Appropriate Uses For SQLite.
Con Some SQL features are missing
SQLite is made to be extremely lightweight and portable, but it still uses SQL. However, some SQL features such as
RIGHT OUTER JOIN and
FOR EACH STATEMENT are missing.