mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
dbplyr vs workflows
A side-by-side editorial comparison of dbplyr and workflows — release velocity, themes, recent moves, and the top alternatives to consider.
dbplyr vs workflows: at a glance
What is dbplyr?
dbplyr ends its two-year backend migration by dropping 1st edition support outright
dbplyr translates dplyr code into SQL, and 2.6.0 closes a migration that has been running since 2023: first-edition backends no longer work at all. The same release converts a long list of soft deprecations into hard failures and removes functions deprecated as far back as 2019. The releases before it were translation-quality work across SQL Server, Redshift, Snowflake, Postgres, Spark and Teradata.
What is workflows?
The tidymodels pipeline grew a third stage, and it happens after the model runs.
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
dbplyr vs workflows: editorial side-by-side
dbplyr
0.0ANALYTICS
dbplyr ends its two-year backend migration by dropping 1st edition support outright
◆ Current state
dbplyr translates dplyr code into SQL, and 2.6.0 closes a migration that has been running since 2023: first-edition backends no longer work at all. The same release converts a long list of soft deprecations into hard failures and removes functions deprecated as far back as 2019. The releases before it were translation-quality work across SQL Server, Redshift, Snowflake, Postgres, Spark and Teradata.
◆ Where it's heading
The package is trading compatibility surface for a smaller, more consistent core it can actually evolve — qualified table names were overhauled in 2.5.0, sql() and ident() were refactored internally, and the cte argument gave way to a single sql_options() entry point. Backend breadth keeps growing at the translation level even as the extension API narrows.
◆ Prediction
With the edition split finally gone, expect the next cycle to spend its budget on dialect translations and the newer Spark/Databricks path rather than on further deprecation.
workflows
0.0ANALYTICS
The tidymodels pipeline grew a third stage, and it happens after the model runs.
◆ Current state
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
◆ Where it's heading
The object is filling out into a complete pipeline description rather than a preprocessing-plus-model pair. Postprocessing is the structural addition — calibration and threshold selection were previously done by hand after prediction, outside anything tidymodels could tune or record — and the fact that it arrived integrated with tunable() and tune_args() rather than as a standalone step is the point. The rest of the arc is the steady tidymodels habit of converting silent guesses into errors.
◆ Prediction
Expect tailor postprocessors to spread through tune and workflowsets next, since the parameter and tuning generics were wired up first, and expect sparse support to extend to more engines after lightgbm.
Alternatives to dbplyr and workflows
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 dbplyr or workflows.
mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk
timetk swallowed anomalize whole, then went quiet for two years
modelbased
modelbased is turning marginal effects into a full contrast grammar
parameters
easystats' parameters package absorbs one more model class every few weeks
See all dbplyr alternatives → · See all workflows alternatives →
Recent activity from dbplyr and workflows
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agodbplyr1st edition backends removed; a wave of deprecations goes defunct ⚡
- 11mo agodbplyrDate and aggregate translation fixes across six SQL dialects
- 11mo agoworkflowsWorkflows gain a postprocessing stage via tailor ⚡
- 1y agoworkflowsSparse matrices work through fit() and predict()
- 2y agodbplyrQualified table names overhauled; I() becomes the simple path
- 2y agoworkflowsaugment() aligns with parsnip; censored regression supported
- 2y agodbplyrPreliminary Databricks Spark SQL backend; join fixes
- 2y agodbplyrdbplyr 2.3.4
- 3y agodbplyrdbplyr 2.3.3
- 3y agoworkflowsRegister tuning generics unconditionally
- 3y agoworkflowsMissing parsnip extensions now error early; unsupervised specs supported
- 3y agoworkflowsMode guessing removed; silent offset handling now errors
Frequently asked questions
What is the difference between dbplyr and workflows?
They serve adjacent needs but don't currently overlap on shipped themes. dbplyr and workflows 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 dbplyr better than workflows?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbplyr and workflows 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 dbplyr?
Top dbplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dbplyr alternatives" section above for the current picks, or visit /alternatives/dbplyr for the full list with editorial commentary on each.
What are the best alternatives to workflows?
Top workflows alternatives in Analytics are ranked by recent ship velocity. Browse the "workflows alternatives" section above for the current picks, or visit /alternatives/workflows-r for the full list with editorial commentary on each.