Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
A side-by-side editorial comparison of Dub and runc — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Dub | runc |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | partner-programs, affiliate-marketing, ai-automation, rewards | container runtime, release candidate, breaking changes, kernel workaround |
| Last editorial update | 7h ago | 1h ago |
| Website | — | Visit → |
Dub adds AI application screening as its partner program controls keep getting finer.
Dub's run since July is almost entirely Dub Partners. Programs can now auto-reject applicants against plain-language criteria, set rewards per partner or per link, pay retainer-style fixed amounts, and let existing partners apply to switch groups. Bounties and email campaigns gained tag scoping and combined conditions, while the link product got one-click DNS setup for Vercel and Cloudflare.
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.
Dub's run since July is almost entirely Dub Partners. Programs can now auto-reject applicants against plain-language criteria, set rewards per partner or per link, pay retainer-style fixed amounts, and let existing partners apply to switch groups. Bounties and email campaigns gained tag scoping and combined conditions, while the link product got one-click DNS setup for Vercel and Cloudflare.
The partner product is moving from commission setup to program operations. Retainers and link-level rewards widen what can be paid for, and AI now appears in two administrative jobs, reward building and application screening. Each release reduces a manual step for program operators.
Expect more AI help in program administration, since reward building and screening shipped within two months of each other. Further reward primitives are also likely given the pace since July.
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 Dub or runc.
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Harness Open Source last shipped in August 2025, on this feed at least
Payload's v4 beta ships every few days, and most of the risk sits in the breaking-change notes
Scalar is testing demand for hosting from inside localhost
Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dub is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. Dub is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 Dub alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dub alternatives" section above for the current picks, or visit /alternatives/dub 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.