← Back to home
Comparison · Analytics

taxizedb vs vcr

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

Shared themes:ropensci

taxizedb vs vcr: at a glance

Featuretaxizedbvcr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestaxonomy, biodiversity-data, sqlite, ropenscitesting, http-mocking, breaking-change, api-cleanup
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is taxizedb?

Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.

taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.

Read the full taxizedb trajectory →

What is vcr?

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

Read the full vcr trajectory →

taxizedb vs vcr: editorial side-by-side

T
taxizedb
ANALYTICS
0.0

Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.

◆ Current state

taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.

◆ Where it's heading

The package is trading convenience for independence. Each release removes another thing that has to be working elsewhere for the package to function: hosted database preparation is gone, and where a provider disappears the package documents it rather than pretending otherwise — db_download_tpl() is now defunct because The Plant List no longer exists, though previously downloaded copies still query fine. Release cadence is slow, with multi-year gaps and a maintainer handover in 2023.

◆ Prediction

Expect further releases to track data sources appearing and disappearing rather than adding features, since that has driven every recent change. Local conversion also shifts cost onto users, so build time and memory for the larger sources are the plausible next thing to need attention.

V
vcr
ANALYTICS
0.0

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

◆ Current state

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

◆ Where it's heading

The package is consolidating after years of additive growth. The 2.0 removals are almost all things that were exported without needing to be, or options that promised behaviour the implementation could not guarantee — check_cassette_names() was deprecated precisely because it cannot be made correct. Cassette maintenance is being simplified too, with re_record_interval now the single mechanism for expiring recordings.

◆ Prediction

Expect the post-2.0 releases to be about migration support and fallout from the removed API, since the breaking list is long enough that reverse dependencies will surface problems. Async support for httr2 stays blocked until req_perform_parallel gains a mocking hook, which the entries note is upstream work.

Alternatives to taxizedb and vcr

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 taxizedb or vcr.

See all taxizedb alternatives → · See all vcr alternatives →

Recent activity from taxizedb and vcr

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

  1. 8mo agovcr2.0 removes the logging API and the exported R6 classes
  2. 9mo agotaxizedbDatabases now built locally from raw data, not the cloud
  3. 1y agovcrMaintainer email address updated
  4. 2y agovcrAdds httr2 support alongside httr and crul
  5. 3y agotaxizedbPatch release for a maintainer change
  6. 3y agovcrDrops compilation; test setup moves back to helper files
  7. 3y agovcrFixes request matching with escaped characters
  8. 5y agovcrvcr_test_path() finds the package root correctly
  9. 5y agotaxizedbtaxa_at() retrieves ancestors at a named rank
  10. 5y agotaxizedbFixes failing tests
  11. 6y agotaxizedbSQLite everywhere, three new sources, taxize verbs ported
  12. 9y agotaxizedbTracks the dplyr split that introduced dbplyr

Frequently asked questions

What is the difference between taxizedb and vcr?

Both compete on the same themes — ropensci — within Analytics. taxizedb and vcr 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 taxizedb better than vcr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. taxizedb and vcr 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 taxizedb?

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

What are the best alternatives to vcr?

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