← Back to home
Comparison · DevOps

distributed vs httpuv

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

Shared themes:maintenance

distributed vs httpuv: at a glance

Featuredistributedhttpuv
SectorDevOpsDevOps
Velocity score5.00.0
Sparks · 30d00
Top themesdistributed-computing, deprecations, breaking-changes, maintenanceweb-server, websockets, shiny, maintenance
Last editorial update1d ago50m ago
WebsiteVisit →Visit →

What is distributed?

Dask's scheduler spent the year deleting deprecated API, not adding surface.

distributed is cutting frequent tags with little in them. The substantive release in the window is 2026.6.0, which removed deprecations across the scheduler, worker, nanny, CLI, security and deploy modules in roughly twenty separate cleanups and moved CI to pixi. 2026.7.0 follows with a breaking scatter change and a scheduler_info() default change; the two most recent tags are a backport and an empty release with no changes at all.

Read the full distributed trajectory →

What is httpuv?

httpuv ships almost nothing, which is what you want from the web server under Shiny

httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.

Read the full httpuv trajectory →

distributed vs httpuv: editorial side-by-side

D5.0

Dask's scheduler spent the year deleting deprecated API, not adding surface.

◆ Current state

distributed is cutting frequent tags with little in them. The substantive release in the window is 2026.6.0, which removed deprecations across the scheduler, worker, nanny, CLI, security and deploy modules in roughly twenty separate cleanups and moved CI to pixi. 2026.7.0 follows with a breaking scatter change and a scheduler_info() default change; the two most recent tags are a backport and an empty release with no changes at all.

◆ Where it's heading

The direction is consolidation. A single maintainer is systematically retiring API that had been deprecated for years, tightening type annotations and chasing flaky tests, while the feature surface stays flat. Python 3.14 support and a PyArrow floor in 2026.1.2 fit the same pattern of keeping the runtime current rather than extending it.

◆ Prediction

With the deprecation sweep largely done and pixi now driving CI, the next releases most likely continue as small breaking cleanups on top of a stable feature set rather than introducing new scheduler capability.

H
httpuv
DEVOPS
0.0

httpuv ships almost nothing, which is what you want from the web server under Shiny

◆ Current state

httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.

◆ Where it's heading

There is no direction here in the usual sense, and that is the honest read: the package is a stable foundation whose releases are triggered by the toolchain moving, by R-devel warnings, or by a threading bug surfacing under load. The one recurring theme with substance is connection reliability - WebSocket keepalive pings, race conditions in the I/O thread - which is what actually breaks Shiny apps in production.

◆ Prediction

Expect continued small releases tracking Rtools, R-devel and mime data, with any substantive change most likely coming from a threading or WebSocket issue reported by Shiny users rather than from planned work.

Alternatives to distributed and httpuv

Other DevOps 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 distributed or httpuv.

See all distributed alternatives → · See all httpuv alternatives →

Recent activity from distributed and httpuv

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

  1. 1mo agodistributedBackport tag extending an earlier fix
  2. 1mo agodistributedEmpty release: no changes
  3. 1mo agodistributedBreaking: scatter stops unpacking custom containers
  4. 2mo agodistributedDeprecated APIs removed across scheduler, worker and CLI
  5. 4mo agodistributedCI pins, type hints and a dashboard CPU fix
  6. 6mo agodistributedPython 3.14 support and a PyArrow 16 floor
  7. 1y agohttpuvServes .wasm as application/wasm; mime table refreshed
  8. 2y agohttpuvrunStaticServer() survives a failed browser launch
  9. 2y agohttpuvRtools build file update and macOS zlib linking fix
  10. 2y agohttpuvFixes an R CMD check warning on error format strings
  11. 2y agohttpuvrunStaticServer() serves a directory of static files
  12. 3y agohttpuvFixes a race condition introduced in 1.6.10

Frequently asked questions

What is the difference between distributed and httpuv?

Both compete on the same themes — maintenance — within DevOps. distributed is currently shipping more aggressively (velocity 5.0 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 distributed better than httpuv?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. distributed is currently shipping more aggressively (velocity 5.0 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 DevOps products to evaluate alongside.

What are the best alternatives to distributed?

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

What are the best alternatives to httpuv?

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