Undertow
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
A side-by-side editorial comparison of OceanBase and SciPy — release velocity, themes, recent moves, and the top alternatives to consider.
OceanBase is rebuilding itself as a RAG backend without giving up the HTAP story
OceanBase Community Edition runs at least five branches in parallel — 4.2.5, 4.3.5, 4.4.1, 4.4.2, 4.6.0 and now 5.0.1 — with feature releases on the newest lines and hotfix trains keeping older LTS branches alive. The centre of gravity in this window is V4.6.0, which added a native SQL hybrid-retrieval interface fusing vector, full-text and scalar predicates in one query and reworked the execution framework behind it. The hotfix branches show where that work is straining: 4.4.1 and 4.3.5 patches are dominated by vector-index bugs — HNSW memory blowups, IVF cache leaks, index rebuilds hanging, planner misjudgements that skip the vector index entirely.
SciPy finished translating itself out of Fortran and now offers a Fortran-free build.
SciPy ships on a six-month major cadence with a long release-candidate tail, and the 1.17/1.18 cycle has been dominated by three structural projects rather than new algorithms. The Fortran-to-C translation is complete, with an experimental Fortran-free build now available to developers. ILP64 BLAS and LAPACK went from initial support in 1.17.0 to three fully supported build modes in 1.18.0. And array API work has spread far enough that stats functions now run under JAX JIT and accept lazy arrays.
OceanBase Community Edition runs at least five branches in parallel — 4.2.5, 4.3.5, 4.4.1, 4.4.2, 4.6.0 and now 5.0.1 — with feature releases on the newest lines and hotfix trains keeping older LTS branches alive. The centre of gravity in this window is V4.6.0, which added a native SQL hybrid-retrieval interface fusing vector, full-text and scalar predicates in one query and reworked the execution framework behind it. The hotfix branches show where that work is straining: 4.4.1 and 4.3.5 patches are dominated by vector-index bugs — HNSW memory blowups, IVF cache leaks, index rebuilds hanging, planner misjudgements that skip the vector index entirely.
Two threads run side by side and neither is being sacrificed. One is AI data infrastructure: hybrid search, sparse vectors, recall evaluation, Document AI and an explicitly named end-to-end RAG package, plus AI Functions that now handle images. The other is the HTAP and availability core: columnar replica routing with consistent reads, primary/standby strong sync at RPO=0 graduating from experimental to supported inside two releases, and V5.0.1 completing online conversion between row, columnar and hybrid storage formats. Note that publication dates on this feed do not match the stated release dates in the entries, so cadence read off timestamps alone will be misleading.
The volume of vector-index defect fixes across three hotfix branches suggests the next releases on the 5.0 line will spend more effort stabilising hybrid search than extending it, with the RAG packaging work more likely to be documented and productised than expanded.
SciPy ships on a six-month major cadence with a long release-candidate tail, and the 1.17/1.18 cycle has been dominated by three structural projects rather than new algorithms. The Fortran-to-C translation is complete, with an experimental Fortran-free build now available to developers. ILP64 BLAS and LAPACK went from initial support in 1.17.0 to three fully supported build modes in 1.18.0. And array API work has spread far enough that stats functions now run under JAX JIT and accept lazy arrays.
SciPy is decoupling itself from its own foundations — the Fortran toolchain, the assumption of 32-bit indexing, and the assumption that arrays are NumPy arrays. Each of those makes SciPy buildable and usable in places it previously was not: environments without a Fortran compiler, problems above the LP64 size limit, and accelerator-backed array libraries. The internal FFT backend swap from pocketfft to ducc0 fits the same pattern of replacing inherited machinery.
The Fortran-free build should move from developer-testing toward a supported option as feedback comes in, and array API coverage will likely keep expanding function by function, as it has each release.
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 OceanBase or SciPy.
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
Betaflight grew a real autopilot: waypoint missions, geofence RTH and MAVLink ground control
QGroundControl rebuilt its flight UI around touch screens, then went quiet for ten months
Pelican now ships roughly once a year, and 4.12 is theme housekeeping
WildFly's quarterly train is really a stability ladder, and OIDC keeps climbing it
Jakarta REST implementation in pure maintenance across two parallel branches.
See all OceanBase alternatives → · See all SciPy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OceanBase is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. OceanBase is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Top OceanBase alternatives in DevOps are ranked by recent ship velocity. Browse the "OceanBase alternatives" section above for the current picks, or visit /alternatives/oceanbase for the full list with editorial commentary on each.
Top SciPy alternatives in DevOps are ranked by recent ship velocity. Browse the "SciPy alternatives" section above for the current picks, or visit /alternatives/scipy for the full list with editorial commentary on each.