ESP-IDF
Espressif keeps five ESP-IDF branches alive and tells you almost nothing in the release notes.
Comparison · DevOps
NSD vs Erlang/OTP
A side-by-side editorial comparison of NSD and Erlang/OTP — release velocity, themes, recent moves, and the top alternatives to consider.
NSD vs Erlang/OTP: at a glance
What is NSD?
Memory work paid off, then a serious SVCB overflow arrived — and Prometheus users get a breaking relabel.
NSD's recent history runs through three arcs. The 4.14.0 release refactored RDATA storage to cut memory footprint, a regression was reported immediately for zones with large RRsets, and 4.14.1 closed that gap so consumption dropped in all cases. In June, 4.14.3 fixed two CVEs, one a heap overflow of up to 65,509 attacker-controlled bytes reachable through a crafted SVCB record. Then 4.15.0 moved zone identity in Prometheus metrics from the metric name into a label, with an explicit warning that current users must adapt. Every release ships as an rc1 with identical notes before the final.
What is Erlang/OTP?
Three OTP branches move as one release train, and SSH and epmd carry the security load.
Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.
NSD vs Erlang/OTP: editorial side-by-side
NSD
0.0DEVOPS
Memory work paid off, then a serious SVCB overflow arrived — and Prometheus users get a breaking relabel.
◆ Current state
NSD's recent history runs through three arcs. The 4.14.0 release refactored RDATA storage to cut memory footprint, a regression was reported immediately for zones with large RRsets, and 4.14.1 closed that gap so consumption dropped in all cases. In June, 4.14.3 fixed two CVEs, one a heap overflow of up to 65,509 attacker-controlled bytes reachable through a crafted SVCB record. Then 4.15.0 moved zone identity in Prometheus metrics from the metric name into a label, with an explicit warning that current users must adapt. Every release ships as an rc1 with identical notes before the final.
◆ Where it's heading
This is a mature authoritative nameserver where the remaining work is footprint, correctness and observability rather than protocol features. The memory refactor and its follow-up show a project willing to ship a structural change and then immediately correct for reported regressions. The SVCB overflow is a reminder that newer record types are where the parsing risk now lives, since the older ones have been fuzzed for two decades. NLnet Labs also rotated its release signing key at the start of 2026 and documents the fingerprint in each announcement.
◆ Prediction
Expect the Prometheus relabeling to generate follow-up fixes as operators hit dashboard breakage, and continued attention to newer record type parsing. The rc-then-final rhythm makes the next release predictable in shape if not in content.
Erlang/OTP
5.0DEVOPS
Three OTP branches move as one release train, and SSH and epmd carry the security load.
◆ Current state
Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.
◆ Where it's heading
The maintenance pattern is unusually strict: 27, 28 and 29 receive the same trouble reports on the same day, so the effective support window is wide and sites on older majors are not being pushed forward by security pressure. Where the fixes land is consistent — ssh, ssl, crypto, public_key and erts account for nearly every changed application across these releases, which is the distribution epmd and the TLS/SSH stack impose on a distributed runtime. The CBC timing mitigation in particular is an old class of attack being closed properly rather than papered over.
◆ Prediction
Expect the next patch trio to follow the same shape — a small set of trouble reports applied to all three branches simultaneously — with ssh and ssl the most likely applications to change. Nothing in these entries indicates feature work landing on the patch branches; that stays on the next major.
Alternatives to NSD and Erlang/OTP
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 NSD or Erlang/OTP.
Apache Seata
Seata's first Apache release is stuck in a voting round, two years after its last shipped version.
Apollo Config
Apollo is grinding down the operational cost of running a config service.
Dapr
Dapr patches three release lines at once and writes root-cause notes for each fix.
Apache bRPC
Apache bRPC keeps widening what it can talk to and what it can run on.
OpenTripPlanner
OpenTripPlanner finished a multi-year migration by deleting its REST API.
See all NSD alternatives → · See all Erlang/OTP alternatives →
Recent activity from NSD and Erlang/OTP
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoErlang/OTPSSH now rejects misaligned packets with a timing-safe discard
- 5d agoErlang/OTPOTP 28 takes the same SSH alignment and epmd fixes
- 5d agoErlang/OTPOTP 27 receives the same erts and ssh patches
- 12d agoErlang/OTP27 July patch touches crypto, ssl, ssh and public_key on OTP 28
- 12d agoErlang/OTPOTP 27 mirrors the 27 July crypto and transport patch
- 12d agoErlang/OTPOTP 29.0.4 carries six CVEs and an epmd DoS mitigation
- 1mo agoNSDPrometheus metrics move zone from metric name to label
- 1mo agoNSDRelease candidate for 4.15.0 with identical notes
- 1mo agoNSDHeap overflow via crafted SVCB records patched
- 4mo agoNSDIXFR processing fix for collated add and delete records
- 4mo agoNSDRelease candidate for the 4.14.2 IXFR fix
- 5mo agoNSDMemory regression from the RDATA refactor closed
Frequently asked questions
What is the difference between NSD and Erlang/OTP?
They serve adjacent needs but don't currently overlap on shipped themes. Erlang/OTP is currently shipping more aggressively (velocity 5.0 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.
Is NSD better than Erlang/OTP?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Erlang/OTP is currently shipping more aggressively (velocity 5.0 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 DevOps products to evaluate alongside.
What are the best alternatives to NSD?
Top NSD alternatives in DevOps are ranked by recent ship velocity. Browse the "NSD alternatives" section above for the current picks, or visit /alternatives/nsd for the full list with editorial commentary on each.
What are the best alternatives to Erlang/OTP?
Top Erlang/OTP alternatives in DevOps are ranked by recent ship velocity. Browse the "Erlang/OTP alternatives" section above for the current picks, or visit /alternatives/erlang-otp for the full list with editorial commentary on each.