Lima
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
A side-by-side editorial comparison of Apache Pinot and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
1.6.0 on 29 October lets operators manage tables through CREATE, DROP and SHOW statements, gives materialized views DDL and single-stage query rewrite, and adds GROUPING SETS, ROLLUP and CUBE to both query engines. Vector search gains IVF_FLAT, IVF_PQ and IVF_ON_DISK backends alongside HNSW. The release also removes legacy pieces: native text and FST indexes, Spark 2 and Presto integrations, and APIs deprecated through 1.3.0.
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
1.6.0 on 29 October lets operators manage tables through CREATE, DROP and SHOW statements, gives materialized views DDL and single-stage query rewrite, and adds GROUPING SETS, ROLLUP and CUBE to both query engines. Vector search gains IVF_FLAT, IVF_PQ and IVF_ON_DISK backends alongside HNSW. The release also removes legacy pieces: native text and FST indexes, Spark 2 and Presto integrations, and APIs deprecated through 1.3.0.
Pinot is moving toward being operated like a SQL database. The multi-stage engine's SQL coverage has grown release by release, and table lifecycle now joins it, while vector backends pull retrieval workloads into the same store. The upgrade cost is real: Java 25 for services, Scala 2.13 for Spark artifacts, and mixed-version limits around SMART aggregation. Federation, the headline of 1.5, doesn't feature in the 1.6 highlights.
Expect materialized-view rewrite to reach the multi-stage engine, since it is single-stage only today. A security patch on 1.6 would match what followed 1.5.0.
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
Other Infra & APIs 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 Pinot or runc.
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
Honeycomb is working on the first ten minutes, not just the incident
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
See all Apache Pinot alternatives → · See all runc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apache Pinot is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Apache Pinot is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Apache Pinot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apache Pinot alternatives" section above for the current picks, or visit /alternatives/apache-pinot for the full list with editorial commentary on each.
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.