I love it when a discussion about one thing I've written points me at the next thing I should be writing about.
NATS is just one of those technologies that seems to be done right. They've implemented all the messaging patterns in a way that just makes it so simple to support complex scenarios that you can't easily do with competing products. Messaging / KVP / Object Storage / Mesh Networking / Multi Tenancy /
And sometimes, the topic I've been planning to write about suddenly becomes topical and I get to explain something a lot of people have been talking (and maybe fighting) about.
I'd been suggesting to my editor at The Stack that I talk about NATS long before the kerfuffle with the CNCF because people like @hvr.endj.in were being so enthusiastic about the project and interesting projects like @wasmcloud.com were building on top of it.
Everyone has their own opinion about the politics of the debate about OSS business models but I figured after all that publicity about the arguments, people would want to know what the technology actually does, so I asked @derekcollison.bsky.social to explain why NATS isn't just another message bus
Really, NATS is more of a Swiss Army knife that does a whole lot of things you need for building IoT and other cloud native workloads that you want to have scale the way infrastructure does...
Simple, speedy, scalable, resilient: the fast, lightweight message broker you’re suddenly hearing a lot about has plenty of competition but stands out for its comprehensive approach to event-driven architecture
CNCF
message broker
event bus
governance
Kubernetes
IoT
distributed systems
edge
Synadia
wasmCloud