NATS.io

Are you a NATS End-User? We'd ❤️ to hear from you! Share your experience with the community in our GitHub Discussion. Thanks to @daprdev for the idea 👏 github.com/nats-io/nats-g…

he first post covers all four, and the one mental model shift that makes every downstream architecture decision easier. If you're building for IIoT, connected fleets, energy systems, or any environment where "the network will always be there" is not a safe assumption: → synadia.com/blog/nats-edge… #EdgeComputing #IIoT #DistributedSystems #NATS

We asked Bruno Baloi — the author of our Living on the Edge white paper — to turn his research into a blog series. More opinionated. More specific. Closer to the real patterns he sees teams get wrong. Post 1 is live. A thread on what's in it 🧵

Excel can be used for ... what? Things like Kafka Streams and Flink are a hell of an investment for the remit of "watching some numbers, doing some arithmetic and publishing the results..". Coupled with @nats_io this is an interesting way to prototype. alexjreid.dev/posts/excel-th…

Follow-up with the agent runtime: #ACP ↔ @nats_io agent layer github.com/TrogonStack/tr… Agent = consumer + command dispatcher

🔥

@taigrr @nats_io Love @nats_io. Just open-sourced this today: github.com/galaxy-io/gnat

Working on acp-nats-stdio in TrogonAI: github.com/TrogonStack/tr… This is the #ACP ↔ @nats_io stdio bridge I’ve been building. Not doing a release victory lap yet, still tightening CI. It’s far enough along to share direction and get early technical feedback. If you build agent/event systems, I’d love your sharpest critique.

One day in the books at #KubeCon Amsterdam - and we've already talked to users running @nats_io... on factory floors in brick and mortar retail in space! Can you beat NATS in space?! Stop by booth 486 and try!

Is it still a one-shot if the shot is preceded by building an deterministic simulation testing environment with failure injection?! Anyway, I'm about to "one-shot" resonate on @nats_io

Turns out @nats_io got everything we need to implement @resonatehqio durable execution: - queues for messaging - key value store for persistence - scheduled messages for timeouts Bonus: With the NATS Execution Engine (Nex) you can run your workflows on NATS as well

@DominikTornow @nats_io @resonatehqio nats is literally goated beyond recognition

@Uber+ @Rivian $1.25B on 50K robotaxis across 25 cities The autonomy strategy runs on a data flywheel. Sensor data from every vehicle feeding back into AI That needs serious infra! Real-time. Edge to cloud. At fleet scale.

Rivian's new RAD team races trucks in the desert and on frozen lakes — then ships what they learn as software updates to every owner. Edge data → real-time intelligence → better product. That's the connected vehicle loop. That's what NATS is built for. roadandtrack.com/news/a70513138… #ConnectedVehicles #EdgeComputing #NATS

Next week is gonna be a big one! We've got fresh swag, plus a brand new product to tell you about 👀 See you in Amsterdam!

NATS Monthly March 2026 🍀 What's inside... 🍀NATS v2.12.5 released, 🍀check out how NATS is being used for AI agents, 🍀a guide on NATS monitoring, 🍀comparing MQTT and NATS for fleet management, and more! synadia.com/newsletter/nat…

Great piece from Stephan Litjens at Nokia — the 'edge for everyone' shift is real and accelerating. One dimension worth adding: once you've committed to local edge infrastructure, the next hard problem is how data actually moves reliably between edge and core — especially when connectivity is intermittent. The challenges Nokia describes (latency, reliability, compliance, cost) don't disappear once you have a private wireless network. They surface again at the messaging layer. Store-and-forward for disconnected devices, security boundaries between edge and core realms, flow control so a factory floor doesn't flood core systems, end-to-end observability across the full topology — these are the architecture decisions that determine whether edge deployments actually deliver on their promise. nokia.com/blog/edge-comp…

@nats_io is so underhyped.

NATS 2.11 added per-message TTL to JetStream, and it quietly removed a lot of stack bloat. Here's how:

We will expand on this too in a future release of the server to allow some very cool use cases. Powerful as it is, but we will continue to make things even better.

Edge-to-core architectures need both: - Event distribution (stateless pub/sub, request-reply) - Event streaming (stateful, durable, replayable streams) - A hybrid event platform supports both modes natively, reducing platform sprawl. #section-4" target="_blank" rel="nofollow noopener">synadia.com/resources/livi…