Omni
Omni ships weekly, and almost every week the headline item is an AI feature
A side-by-side editorial comparison of Apache Druid and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Apache Druid | Fulcrum |
|---|---|---|
| Sector | Analytics, Infra & APIs | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | real-time-analytics, apache-project, quarterly-releases, upgrade-compatibility | field-data-collection, esri-arcgis, offline-maps, mobile-releases |
| Last editorial update | 14d ago | 4h ago |
| Website | Visit → | — |
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.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
The mapping stack is the whole story right now: ArcGIS SDK 300.0.0 on iOS, the latest ArcGIS and deck.gl on web, and a hard cutover date after which any organization still defaulting to Google Maps is switched to Esri automatically. The mobile releases in this window are almost entirely map and location fixes — basemap loading, offline symbol styling, location resolution that blocked saves. On-device inference quietly changed format, dropping ONNX.
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 mapping stack is the whole story right now: ArcGIS SDK 300.0.0 on iOS, the latest ArcGIS and deck.gl on web, and a hard cutover date after which any organization still defaulting to Google Maps is switched to Esri automatically. The mobile releases in this window are almost entirely map and location fixes — basemap loading, offline symbol styling, location resolution that blocked saves. On-device inference quietly changed format, dropping ONNX.
One platform bet runs through everything: Esri as the single map engine, with Google's satellite, hybrid, and street imagery retained as basemap options so the migration costs users imagery choice, not capability. The current release cadence is stabilization work paying down that migration rather than new ground.
Expect map and location fixes to keep dominating releases through the September 1 cutover, with the Esri-only capabilities already listed — snapping, ArcGIS Feature Service connectivity, offline basemaps — becoming the default surface rather than the alternative one.
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 Fulcrum.
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Amundsen's last release was a config flag, and the feed has been silent for two years
See all Apache Druid alternatives → · See all Fulcrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 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. Fulcrum is currently shipping more aggressively (velocity 6.3 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 Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.