If you already have Keccak (SHA-3) around for ML-KEM and ML-DSA, and you want to use it for hashing, draw 32 bytes from SHAKE128.

@FiloSottile Is this because SHAKE supports arbitrary length?
(As a non cryptographer…) Are the preimage discussions around SHAKE not relevant in the “Hash Function” context?

score 1 · canonical

I’ve experienced Kafka being used as a job queue at various places, and to me it typically felt like an awkward fit (or had lots of userspace code to deal with various replay scenarios).
I think I would have probably use NATS/jetsteam instead.

score 1 · canonical

HTTP/2 is an improvement, but muxing over a single tcp connection is still problematic as HTTP/2 still exhibits head-of-the-line blocking at the TCP layer – I imagine in really high RPS systems it would still be suboptimal. HTTP/3 should provide a big improvement though in that regard.

score 1 · canonical

I imagine these days using zstd instead of gzip would widen the gap even further.

score 2 · canonical