Synadia

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…

We've seen this play out across industrial IoT, energy, and manufacturing — check out this white paper walking through key patterns: separation of edge and core realms, hybrid eventing, full event mesh topology, and more. synadia.com/resources/livi…

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…

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.

The bigger story is simplification: fewer systems to deploy, monitor, secure, and get paged on at 2am synadia.com/blog/per-messa…

Sessions, cache entries, presence signals live in the same JetStream streams your events already use No... extra cleanup workers cron jobs sweeping stale state deadlock recovery logic because an expired lock never got cleaned up separate system just to hold short-lived data A crashed job runner? Its lock expires automatically A disconnected device? Its presence key disappears on its own A stale session? Gone when it should be

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

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…

“What looks like a protocol choice quickly becomes an operations choice.” #edge #edgeai #dataengineering #machinelearning #opensource #mqtt #natsio #fleet #fleetmanagement #ai #agenticai #iot

As Synadia pushes to help our customers connect data from the physical world to Intelligence, MQTT plays a critical role here. Did you know that @nats_io can natively except MQTT connections? If this sounds familiar check out the below post, worth a quick read.

NATS: One binary, same security model, edge to cloud. synadia.com/blog/nats-vs-m…

Now you have N independent MQTT instances, each with separate ACLs, monitoring, and failure points. NATS handles all of this in a single system. Leaf nodes handle local traffic locally and buffer through disconnects. JetStream provides persistence + replay w/o a sidecar.

Managing fleets of edge devices with MQTT? Then you're probably shipping 𝘮𝘰𝘳𝘦 than just MQTT. Durable buffering stream replay, and command-response patterns aren't native, so teams...

"It was a great experience. Great people. I love working with Evil Martians." Wally Quevedo from @synadia shares his experience working with our team and highlights @Envek's contributions to the project. youtu.be/iej5C4Z5LEk?si…

Pull or Push? How should you set up monitoring for your NATS systems? How they work, when to use each, tradeoffs Get the whole story: synadia dot com slash monitoring

A platform bridging edge and core should support four flow control capabilities: 1. Subject/topic filtering 2. Subject mapping / traffic shaping 3. Dynamic load distribution (weighted routing) 4. Varied consumption models (push vs pull) #section-3" target="_blank" rel="nofollow noopener">synadia.com/resources/livi…