[freakynit]

Excellent. We already tested at okayish scale of 5 million messages per minute, with each message being less than 1KiB. Do note that NATS can easily handle 100x this scale. It's just what we had tested during initial days.

[bobkb]

Wow!

I have a stupid question - as I understand NATS works very well as a “message” pipe/bus. Anyway to get Redis type cache functionality as well ? Is it something possible ?

[freakynit]

JetStream (not NATS) has a built-in key/value store. Relevant thread (old, from 2023): https://github.com/nats-io/nats.go/discussions/1507

someone did some benchmarks in 2025:

    nats bench kv put --size="128" --msgs 1000000 --storage file
    1m3s → Pub stats: 15,656 msgs/sec ~ 1.91 MB/sec
    
    nats bench kv get --size="128" --msgs 1000000
    59s → Sub stats: 16,720 msgs/sec ~ 2.04 MB/sec

I have personally not used this though.

[bobkb]

Thank you! Jetstream looks useful. For a platform which is production our Redis costs are getting prohibitively high. I was on the look for alternatives and perhaps in the software reliability tool [0] I am buildin try out Jetstream.

[0] https://github.com/bobinson/vulture

[freakynit]

Cool... "vulture" looks pretty good... especially more now-a-days. Thanks..

I also maintain these sites for npm related attacks (since there have been so many since past 1.5 years):

1. Techniques exploited: https://npm-supply-chain-attack-techniques.pagey.site/

2. Documented attacks: https://npm-supply-chain-attacks-25-26.pagey.site/

[withinboredom]

I’d also recommend looking at Swytch (docs.getswytch.com, particularly the economics page).

Disclosure: I’m a founder.