When comparing SQLite vs ArangoDB, the Slant community recommends SQLite for most people. In the question“What are the best databases to use for Node.js applications?” SQLite is ranked 6th while ArangoDB is ranked 10th. The most important reason people chose SQLite is:
Ranked in these QuestionsQuestion Ranking
Pro Great language support
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.
SQLite is largely self-contained. It requires very minimal support from external libraries or from the operating system.
SQLite is also only 350KiB in size.
Pro Not unnecessarily fiddly
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 Easy cluster setup
Pro Supports joins
Unlike many NoSQL databases, ArangoDB does support joins in AQL queries.
Pro Powerful Java Driver (Sync & Async)
ArangoDB has a very good Java Driver for synchronous and asynchronous. In addition the team there is working on a Spring Data integration.
Pro Transaction save
You can use ACID Transactions for short and small data retrieval and/or modification operations in ArangoDB.
Pro Document and graph-orientend
You can model your data as documents or as a graph - no data model lock-in. You can even combine both models and use them in a single AQL query.
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.