better-sqlite3 is much faster than node-sqlite3 in most cases, and just as fast in all other cases. better-sqlite3 is simpler to use, and it provides nice utilities for some operations that are very difficult or impossible in node-sqlite3. better-sqlite3 does it the JavaScript way, allowing the garbage collector to worry about memory management. node-sqlite3 exposes low-level (C language) memory management functions. It also causes mutex thrashing which has devastating effects on performance. That's not only bad design, but it wastes tons of resources. node-sqlite3 uses asynchronous APIs for tasks that are either CPU-bound or serialized. pragma ( 'journal_mode = WAL' ) Why should I use this instead of node-sqlite3? Import Database from 'better-sqlite3' const db = new Database ( 'foobar.db', options ) db. You can verify these results by running the benchmark yourself. 
If your company uses better-sqlite3, ask your manager to consider supporting the project: Long nights and weekends were spent keeping this project strong and dependable, with no ask for compensation or funding, until now. Worker thread support (for large/slow queries)īetter-sqlite3 is used by thousands of developers and engineers on a daily basis.64-bit integers (invisible until you need them).
Support for user-defined functions, aggregates, virtual tables, and extensions.Easy-to-use synchronous API (better concurrency than an asynchronous API.High performance, efficiency, and safety.
The fastest and simplest library for SQLite3 in Node.js.
0 kommentar(er)
