timetk
timetk swallowed anomalize whole, then went quiet for two years
Comparison · Analytics
Delta Lake vs workflows
A side-by-side editorial comparison of Delta Lake and workflows — release velocity, themes, recent moves, and the top alternatives to consider.
Delta Lake vs workflows: at a glance
What is Delta Lake?
Delta Lake's public releases are patch work while Databricks kernel builds fill the feed.
Two kinds of entry dominate: numbered patch releases on the 3.3 and 4.3 lines, and near-daily Databricks kernel build tags that carry a single commit message each. The patch releases are targeted correctness work — a metadata cleanup that could delete transaction log files still needed to reconstruct versions inside the retention window, a Delta Sharing cache refresh that dropped deletion-vector URL mappings, an OAuth key-casing bug in the REST Catalog, and S3A fast-listing through FilterFileSystem wrappers. The 3.3.3 release also declines to publish delta-iceberg, leaving UniForm users on the prior patch.
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.
Delta Lake vs workflows: editorial side-by-side
Delta Lake
5.0ANALYTICS
Delta Lake's public releases are patch work while Databricks kernel builds fill the feed.
◆ Current state
Two kinds of entry dominate: numbered patch releases on the 3.3 and 4.3 lines, and near-daily Databricks kernel build tags that carry a single commit message each. The patch releases are targeted correctness work — a metadata cleanup that could delete transaction log files still needed to reconstruct versions inside the retention window, a Delta Sharing cache refresh that dropped deletion-vector URL mappings, an OAuth key-casing bug in the REST Catalog, and S3A fast-listing through FilterFileSystem wrappers. The 3.3.3 release also declines to publish delta-iceberg, leaving UniForm users on the prior patch.
◆ Where it's heading
The project is stabilising two supported lines in parallel rather than moving the format forward in these entries, and the recurring theme is metadata and log durability — the parts of Delta that silently break time travel and CDF when they are wrong. Kernel work continues in the build tags, most visibly treating _last_checkpoint as opaque JSON. The unpublished UniForm artifact is the one open thread with a stated follow-up plan.
◆ Prediction
A follow-up patch that restores the delta-iceberg artifact for the 3.3 line is the clearest next step; otherwise expect the kernel build cadence to continue between numbered releases.
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 Delta Lake 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 Delta Lake or workflows.
modelbased
modelbased is turning marginal effects into a full contrast grammar
parameters
easystats' parameters package absorbs one more model class every few weeks
tidyposterior
A finished Bayesian model-comparison package in pure maintenance mode
tidypredict
tidypredict now translates the gradient-boosting libraries people actually deploy
tidyclust
tidyclust just tripled the model types it can fit, and handed finalization back to tune
See all Delta Lake alternatives → · See all workflows alternatives →
Recent activity from Delta Lake and workflows
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoDelta LakeLog-retention and Delta Sharing cache fixes; UniForm jar not published
- 13d agoDelta LakeDatabricks kernel build tag (2026-07-30)
- 1mo agoDelta LakeKernel build tag: _last_checkpoint captured as opaque JSON
- 1mo agoDelta LakeDelta Lake 4.3.1
- 1mo agoDelta LakeDatabricks kernel build tag (2026-07-07)
- 1mo agoDelta LakeDatabricks kernel build tag, DBI variant (2026-07-06)
- 11mo agoworkflowsWorkflows gain a postprocessing stage via tailor ⚡
- 1y agoworkflowsSparse matrices work through fit() and predict()
- 2y agoworkflowsaugment() aligns with parsnip; censored regression supported
- 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 Delta Lake and workflows?
They serve adjacent needs but don't currently overlap on shipped themes. Delta Lake 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 Delta Lake better than workflows?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Delta Lake 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 Analytics products to evaluate alongside.
What are the best alternatives to Delta Lake?
Top Delta Lake alternatives in Analytics are ranked by recent ship velocity. Browse the "Delta Lake alternatives" section above for the current picks, or visit /alternatives/delta-lake 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.