Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of Apache Druid and Delta Lake — release velocity, themes, recent moves, and the top alternatives to consider.
Druid ships a large major roughly every quarter and lets the release notes do the talking.
The feed alternates release-candidate tags with the majors they become: 35.0.1 in December, 36.0.0 in February, 37.0.0 in May. The majors are big and diffuse — 37.0.0 counts over 255 changes from 29 contributors, 36.0.0 over 189 from 34 — and are summarised by contributor counts and pointers to upgrade notes rather than headline features. The one patch in the window fixed segment-drop file descriptors leaking until process exit, which is the kind of detail that tells you who runs this: operators with long-lived clusters.
A 4.4.0 tag appears, but the feed carries only its release plumbing
The newest entry is the commit that tagged 4.4.0 — a version.sbt bump plus a local Maven overwrite setting needed for cross-Spark publishing, and it states outright that there are no runtime behaviour changes. The 4.4.0 release notes themselves have not reached this feed, so what the minor version actually contains is not readable here. Behind it sit two patch releases doing targeted correctness work: 3.3.3 on transaction log retention and Delta Sharing cache, 4.3.1 on Delta REST Catalog OAuth and S3A listing, interleaved with near-daily Databricks kernel build tags.
The feed alternates release-candidate tags with the majors they become: 35.0.1 in December, 36.0.0 in February, 37.0.0 in May. The majors are big and diffuse — 37.0.0 counts over 255 changes from 29 contributors, 36.0.0 over 189 from 34 — and are summarised by contributor counts and pointers to upgrade notes rather than headline features. The one patch in the window fixed segment-drop file descriptors leaking until process exit, which is the kind of detail that tells you who runs this: operators with long-lived clusters.
This is a mature Apache project on a predictable cadence, where each release aggregates hundreds of contributions instead of pursuing a theme. Every major carries explicit incompatible-changes and upgrade notes, so compatibility management is treated as a first-class part of shipping. Nothing in the feed points toward a directional shift; the signal is steadiness.
On this cadence the next major and its release candidate are due within a quarter of 37.0.0, likely with a similar volume of changes. What those changes contain cannot be inferred — the entries deliberately defer detail to the linked notes.
The newest entry is the commit that tagged 4.4.0 — a version.sbt bump plus a local Maven overwrite setting needed for cross-Spark publishing, and it states outright that there are no runtime behaviour changes. The 4.4.0 release notes themselves have not reached this feed, so what the minor version actually contains is not readable here. Behind it sit two patch releases doing targeted correctness work: 3.3.3 on transaction log retention and Delta Sharing cache, 4.3.1 on Delta REST Catalog OAuth and S3A listing, interleaved with near-daily Databricks kernel build tags.
The project keeps two supported lines stable in parallel while the format work happens elsewhere, and the durable theme across these patches is metadata and log correctness — the failures that silently break time travel and CDF rather than throwing. The 4.4.0 prep notes one thing worth watching: artifacts are now published across Spark 4.0, 4.1 and 4.2 stages, so the cross-Spark support matrix is widening even as the release content stays out of view.
The 4.4.0 release notes should follow this tag and reveal what the minor version carries; until they do the entries support no read on its direction. The unresolved delta-iceberg artifact gap on the 3.3 line still has no follow-up here.
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 Apache Druid or Delta Lake.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
See all Apache Druid alternatives → · See all Delta Lake alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top Apache Druid alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache Druid alternatives" section above for the current picks, or visit /alternatives/apache-druid for the full list with editorial commentary on each.
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.