r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
nodbi vs pharmaverseadam
A side-by-side editorial comparison of nodbi and pharmaverseadam — release velocity, themes, recent moves, and the top alternatives to consider.
nodbi vs pharmaverseadam: at a glance
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.
What is pharmaverseadam?
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
nodbi vs pharmaverseadam: editorial side-by-side
nodbi
0.0ANALYTICS
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.
pharmaverseadam
0.0ANALYTICS
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
◆ Current state
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
◆ Where it's heading
Coverage tracks the pharmaverse's own therapeutic-area expansion with a lag of one release: pediatrics arrived in 1.1.0, metabolic in 1.2.0, neurology in 1.3.0. The other consistent thread is a slow move off development versions — 1.1.0 and 1.2.0 both had to pin unreleased upstream builds to get working templates, while 1.3.0 cites released versions throughout. Reorganising the reference page by therapeutic area is the same maturation showing up in documentation.
◆ Prediction
Expect the next release to follow the established pattern — a refresh against current upstream versions plus datasets from whichever admiral therapeutic-area package reaches a stable release next.
Alternatives to nodbi and pharmaverseadam
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 pharmaverseadam.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all nodbi alternatives → · See all pharmaverseadam alternatives →
Recent activity from nodbi and pharmaverseadam
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agopharmaverseadamNeurology and anti-drug antibody datasets added
- 8mo agonodbijsonb_tree adopted; $in string queries and duplicate _id handling fixed
- 11mo agopharmaverseadamMetabolic therapeutic area datasets arrive
- 1y agonodbiDuckDB version parsing and listfields fix
- 1y agonodbidocdb_query reworked for DuckDB 1.3.0
- 1y agonodbiNDJSON writing delegated to DuckDB's internal function
- 1y agonodbiQuery results get consistent column types; fast NDJSON import reaches SQLite and Postgres ⚡
- 1y agopharmaverseadamPediatric ADVS added in an ad-hoc refresh
- 1y agonodbiQuery and file-import speedups via newer DuckDB features
- 2y agopharmaverseadam1.0 declares the dataset collection stable
- 2y agopharmaverseadamFirst release of the ADaM dataset collection
Frequently asked questions
What is the difference between nodbi and pharmaverseadam?
They serve adjacent needs but don't currently overlap on shipped themes. nodbi and pharmaverseadam 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 pharmaverseadam?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nodbi and pharmaverseadam 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 pharmaverseadam?
Top pharmaverseadam alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaverseadam alternatives" section above for the current picks, or visit /alternatives/pharmaverseadam for the full list with editorial commentary on each.