← Back to home
Comparison · Analytics

crul vs sofa

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

Shared themes:ropenscitest-infrastructure

crul vs sofa: at a glance

Featurecrulsofa
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themeshttp-client, async, mocking, ropenscicouchdb, database-client, r-package, ropensci
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is crul?

crul took mocking back from webmockr and made it a property of the client itself

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

Read the full crul trajectory →

What is sofa?

A CouchDB client for R whose recent work is all test infrastructure, not new routes.

sofa wraps the CouchDB HTTP API for R — database and document CRUD, Mango queries and indexes, design documents, replication, and attachments, organized around a Cushion connection object. Feature development effectively stopped after 0.4.0 brought CouchDB v3 compatibility in 2020. The two 2026 releases are a testing and packaging overhaul: 0.4.1 rebuilt the suite around a crul-mocked fake CouchDB so tests no longer need Cloudant or a local Docker instance, reaching 100% coverage, and 0.4.2 cleared CRAN check notes.

Read the full sofa trajectory →

crul vs sofa: editorial side-by-side

C
crul
ANALYTICS
0.0

crul took mocking back from webmockr and made it a property of the client itself

◆ Current state

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

◆ Where it's heading

The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.

◆ Prediction

With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.

S
sofa
ANALYTICS
2.5

A CouchDB client for R whose recent work is all test infrastructure, not new routes.

◆ Current state

sofa wraps the CouchDB HTTP API for R — database and document CRUD, Mango queries and indexes, design documents, replication, and attachments, organized around a Cushion connection object. Feature development effectively stopped after 0.4.0 brought CouchDB v3 compatibility in 2020. The two 2026 releases are a testing and packaging overhaul: 0.4.1 rebuilt the suite around a crul-mocked fake CouchDB so tests no longer need Cloudant or a local Docker instance, reaching 100% coverage, and 0.4.2 cleared CRAN check notes.

◆ Where it's heading

This is a rOpenSci package being brought back to a maintainable state rather than extended. The 0.4.1 decision to mock the server is the consequential one — it decouples CI from a live CouchDB, which is what made the cross-platform GitHub Actions workflow and full coverage possible at all. Two genuine bugs surfaced in that process, in db_replicate() URL construction against non-Cloudant servers and db_alldocs(disk=) not returning the documented file path, suggesting the untested paths had drifted.

◆ Prediction

With the test harness now self-contained, the next plausible move is catching up on CouchDB routes added since v3 rather than further infrastructure work, though nothing in these entries commits to it.

Alternatives to crul and sofa

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 crul or sofa.

See all crul alternatives → · See all sofa alternatives →

Recent activity from crul and sofa

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

  1. 21d agosofaCRAN check notes and metadata corrections
  2. 2mo agosofaTests moved to a mocked CouchDB, coverage to 100%
  3. 1y agocrulMocking becomes a client parameter, independent of webmockr
  4. 2y agocrulAsync requests become mockable through webmockr
  5. 2y agocrulDocumentation fixes and test helper tweak
  6. 3y agocrulHTTP retries reach the async classes
  7. 3y agocrulClearer error for mismatched urls and disk lengths
  8. 4y agocrulAsyncQueue gains response accessors; results print as a summary
  9. 6y agosofaCouchDB v3 support, doc_upsert() and bulk get
  10. 8y agosofaMango index management and batched design search
  11. 9y agosofasofa v0.2.0

Frequently asked questions

What is the difference between crul and sofa?

Both compete on the same themes — ropensci, test-infrastructure — within Analytics. sofa is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is crul better than sofa?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sofa is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to crul?

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

What are the best alternatives to sofa?

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