← Back to home
Comparison · Analytics

nodbi vs pkglite

A side-by-side editorial comparison of nodbi and pkglite — release velocity, themes, recent moves, and the top alternatives to consider.

nodbi vs pkglite: at a glance

Featurenodbipkglite
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdocument-databases, json, duckdb, sqliter-packages, pharma-submissions, packaging, file-handling
Last editorial update50m ago1h ago
WebsiteVisit →Visit →

What is nodbi?

One document API over six databases, and every release is spent absorbing their JSON engines' churn

nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.

Read the full nodbi trajectory →

What is pkglite?

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

Read the full pkglite trajectory →

nodbi vs pkglite: editorial side-by-side

N
nodbi
ANALYTICS
0.0

One document API over six databases, and every release is spent absorbing their JSON engines' churn

◆ Current state

nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.

◆ Where it's heading

Two threads dominate. The first is performance, pursued backend by backend: fast direct NDJSON import moved from DuckDB-only to SQLite and PostgreSQL, query refactors chasing each DuckDB release, and the removal of expensive tree-walking where a cheaper path exists. The second is making results predictable — consistent column types, version checks on the database backend, clearer messages when a Postgres database does not exist yet or when column names contain the dots nodbi reserves for JSON paths.

◆ Prediction

Given that most recent releases are triggered by DuckDB and RSQLite version changes, the next one likely follows the same pattern — adopting a new JSON function or working around a slow one. The duplicate-_id handling added in 0.14.0 suggests NDJSON ingestion edge cases are the current active area.

P
pkglite
ANALYTICS
0.0

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

◆ Current state

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

◆ Where it's heading

The failure mode this package cares about is silent — misclassify a binary file as text and the round trip corrupts it, misclassify text as binary and it bloats or drops. So the work is empirical rather than architectural: mine real packages for what extensions actually appear, then widen coverage where specific ecosystems break the pattern. Stan interfaces via rstan brought `src/Makevars` and `src/Makefile` handling; machine learning frameworks brought their own binary formats. Dependencies have gone the other way, with cli removed and replaced by internal equivalents.

◆ Prediction

Expect the next substantive release to widen file specification coverage again for whatever package family the maintainers find breaking the default discovery, since that has been the content of every non-maintenance release for four years.

Alternatives to nodbi and pkglite

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either nodbi or pkglite.

See all nodbi alternatives → · See all pkglite alternatives →

Recent activity from nodbi and pkglite

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agopkgliteMaintainer email and CI workflow updates
  2. 8mo agonodbijsonb_tree adopted; $in string queries and duplicate _id handling fixed
  3. 1y agonodbiDuckDB version parsing and listfields fix
  4. 1y agonodbidocdb_query reworked for DuckDB 1.3.0
  5. 1y agonodbiNDJSON writing delegated to DuckDB's internal function
  6. 1y agonodbiQuery results get consistent column types; fast NDJSON import reaches SQLite and Postgres
  7. 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
  8. 1y agonodbiQuery and file-import speedups via newer DuckDB features
  9. 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
  10. 2y agopkgliteTest helpers moved to helper.R
  11. 3y agopkgliteMore file types recognised; cli dependency dropped
  12. 5y agopkgliteFile collections gain merge, prune, and a tests template

Frequently asked questions

What is the difference between nodbi and pkglite?

They serve adjacent needs but don't currently overlap on shipped themes. nodbi and pkglite are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is nodbi better than pkglite?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nodbi and pkglite are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to nodbi?

Top nodbi alternatives in Analytics are ranked by recent ship velocity. Browse the "nodbi alternatives" section above for the current picks, or visit /alternatives/nodbi for the full list with editorial commentary on each.

What are the best alternatives to pkglite?

Top pkglite alternatives in Analytics are ranked by recent ship velocity. Browse the "pkglite alternatives" section above for the current picks, or visit /alternatives/pkglite for the full list with editorial commentary on each.