NyxJ 2.1.0 is out, and it is a release about making the platform trustworthy under real conditions rather than adding surface area. The 2.0.0 release introduced the service layer; 2.1.0 hardens it.
This article walks through the main additions: per-client token-bucket rate limiting keyed by X-API-Key or IP, an idle connection timeout that also defeats slowloris clients, default security headers, and request correlation built on X-Request-Id and W3C traceparent. We then look at the key-value write-ahead log and its crash recovery model, the switch of cluster gossip to MessagePack (protocol v2), and the new CLI capabilities — global --sort-keys and --ascii flags, multi-file validation with file:line:col errors, CI-friendly exit codes, and a watch command.
The most instructive part is the fuzzing work. Harnesses now cover the parser, repair, SAX, NyxQuery, JSON Patch, JSON Schema, MessagePack and UTF-8 validation, with invariant checks and a seed corpus. They found and fixed three bugs present in 2.0.0: an unterminated buffer read in nyxj_diff when the whole document was replaced, a 511-byte limit on JSON Pointer tokens that made long-key patches inapplicable, and a MessagePack decoder that accepted maps and arrays as map keys, letting a 169-byte message stall a service.
Everything is backward compatible with 2.0.0, the test suite now exceeds 600 checks, and binaries ship for Linux, macOS, Windows and WebAssembly.

Top comments (0)