RethinkDB vs SQLite: What are the differences?
What is RethinkDB? JSON. Scales to multiple machines with very little effort. Open source. RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.
What is SQLite? A software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.
RethinkDB and SQLite can be primarily classified as "Databases" tools.
"Powerful query language" is the top reason why over 46 developers like RethinkDB, while over 151 developers mention "Lightweight" as the leading cause for choosing SQLite.
RethinkDB is an open source tool with 22.3K GitHub stars and 1.73K GitHub forks. Here's a link to RethinkDB's open source repository on GitHub.
According to the StackShare community, SQLite has a broader approval, being mentioned in 313 company stacks & 470 developers stacks; compared to RethinkDB, which is listed in 37 company stacks and 25 developer stacks.
What is RethinkDB?
What is SQLite?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using RethinkDB?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We initially chose RethinkDB because of the schema-less document store features, and better durability resilience/story than MongoDB In the end, it didn't work out quite as we expected: there's plenty of scalability issues, it's near impossible to run analytical workloads and small community makes working with Rethink a challenge. We're in process of migrating all our workloads to PostgreSQL and hopefully, we will be able to decommission our RethinkDB deployment soon.
SQLite is a tricky beast. It's great if you're working single-threaded, but a Terrible Idea if you've got more than one concurrent connection. You use it because it's easy to setup, light, and portable (it's just a file).
In Paperless, we've built a self-hosted web application, so it makes sense to standardise on something small & light, and as we don't have to worry about multiple connections (it's just you using the app), it's a perfect fit.
For users wanting to scale Paperless up to a multi-user environment though, we do provide the hooks to switch to PostgreSQL .
Used during the "build process" of Coolfront Mobile's Flat rate search engine database. Flat rate data that resides in Salesforce is transformed using SQLite into a format that is usable for our mobile Flat rate search engine (AKA: Charlie).
RDBTools is a self-hosted application, and it is important that the installation process is simple. With SQLite, we create a new database file for every analysis. Once the analysis is done, the SQLite file can be thrown away easily.
High-speed update-aware storage used in our region server infrastructure; provides a good middle layer for storage of rapidly modified information.
All the dynamic data (i.e.: jobs) is stored in a simple SQLite database.
Все динамические данные (вакансии) хранятся в простой SQLite БД.
There's really no call for something heavier for this site. SQLite is simple, easy to use and quite reliable given its age.
Main database, using it in multiple datacenters in an active-active configuration.