Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Comparison · Infra & APIs
Jaeger vs runc
A side-by-side editorial comparison of Jaeger and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Jaeger vs runc: at a glance
What is Jaeger?
Jaeger's query service learns to search individual spans, not just whole traces.
Jaeger 2.21 and 2.22 extend the 2.x storage and query rework. ClickHouse storage moved to a stable feature gate in 2.21, and the release removed v1 HTTP endpoints the UI no longer calls. In 2.22 the query service gains FindSpans with RFC 0014 pagination, Elasticsearch span search, and structured filters promoted to beta, while native Elasticsearch trace summaries go stable.
What is runc?
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.
Jaeger vs runc: editorial side-by-side
Jaeger
2.5INFRA · APIS
Jaeger's query service learns to search individual spans, not just whole traces.
◆ Current state
Jaeger 2.21 and 2.22 extend the 2.x storage and query rework. ClickHouse storage moved to a stable feature gate in 2.21, and the release removed v1 HTTP endpoints the UI no longer calls. In 2.22 the query service gains FindSpans with RFC 0014 pagination, Elasticsearch span search, and structured filters promoted to beta, while native Elasticsearch trace summaries go stable.
◆ Where it's heading
The earlier trace-summaries work made search cheaper; span search changes what can be asked. Pagination and structured filters give both the UI and MCP clients a way to query without pulling whole traces. MCP keeps getting practical limits and input checks, and search_traces no longer needs a service name on backends that declare support for that.
◆ Prediction
Expect span search to spread beyond Elasticsearch and memory storage, and structured filters to move from beta to stable as other gates have. Further removal of v1 surface is likely, since 2.21 already started it.
runc
2.5INFRA · APIS
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Jaeger and runc
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 Jaeger or runc.
Okta
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Gitness
Harness Open Source last shipped in August 2025, on this feed at least
Payload CMS
Payload's v4 beta ships every few days, and most of the risk sits in the breaking-change notes
Scalar
Scalar is testing demand for hosting from inside localhost
Incus
Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration
Recent activity from Jaeger and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 26d agoJaegerSpan search and pagination reach the query service
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoJaegerClickHouse goes stable; unused v1 HTTP endpoints removed
- 3mo agoJaegerMCP merges into the query service; Elasticsearch 6 support removed ⚡
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix
- 5mo agoJaegerLightweight trace-summaries endpoint arrives in the v3 API
- 5mo agoJaegerHeader forwarding to storage backends and UI base-path autodetection
- 7mo agoJaegerClock-skew and jitter fixes; metrics storage exposed to the UI
Frequently asked questions
What is the difference between Jaeger and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Jaeger and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Jaeger better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jaeger and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Jaeger?
Top Jaeger alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Jaeger alternatives" section above for the current picks, or visit /alternatives/jaeger for the full list with editorial commentary on each.
What are the best alternatives to runc?
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.