Synadia

Full on-demand workshop here synadia.com/lp/rethinkconn…

cold block faults sparse filter scans wildcard walks across huge subject spaces. Plus a live performance demo and a running list of bad ideas to avoid. If you're ready to push NATS JetStream to the limits, this is the on-demand workshop for you.

If NATS were a Swiss Army knife, most teams would be using it as... a knife. Publish, subscribe, done. Meanwhile the corkscrew, the saw, and the weird little hook thing go untouched:

Resonate is partnering with @synadia to bring durable execution natively to NATS.IO Follow the origin story at @aiDotEngineer (Link below)

Resonate Distributed Async Await is an open protocol instead of a proprietary implementation. Resonate is partnering with @synadia to bring durable execution natively to @nats_io. Run workflows and agents on nothing but NATS. x.com/resonatehqio/s…

Always been proud of our approach around security and that it needs to be a first class citizen through out @nats_io

@nats_io Full workshop here 👉 synadia.com/lp/rethinkconn…

Turning on auth in NATS takes one line. But managing identity, permissions, & key rotation across a fleet, without rolling a single server? That's where your @NATS_io security posture is defined See how to go from a wide-open server to decentralized, dynamic auth that scales

@nats_io It's hands-on and demo-driven, right down to watching unencrypted traffic on the wire and then locking it down, and ends with a practical hardening checklist synadia.com/lp/rethinkconn…

@nats_io → Can connection-time auth decisions be delegated to your own service: OIDC, LDAP, your user store → When a credential leaks, can you revoke/rotate it across the whole system, fast → Do you actually know where you stand today: no auth, basic hardening, or full operator mode

Get these boundaries right and the edge becomes a source of resilience and leverage — the same design that works in the demo keeps working in production. If you're running NATS anywhere near the edge, this is the one to watch and learn from.

Connecting a single edge device or site to your NATS hub takes five minutes. Designing a fleet that still behaves when five devices become five million... that's where things get interesting.

@nats_io Check out our new vid to see how priority consumer groups work — and how they can simplify and harden your architecture at the same time. youtu.be/3KBFdUXYpyY?si…

𝗧𝗶𝗲𝗿𝗲𝗱 𝗽𝗼𝗼𝗹𝘀 𝘁𝗵𝗮𝘁 𝗳𝗮𝗶𝗹 𝗼𝘃𝗲𝗿 𝗶𝗻𝘀𝘁𝗮𝗻𝘁𝗹𝘆. A preferred set of workers owns the work while it's keeping up; a fallback tier steps in the moment it slows or disappears. No threshold to tune, no delay. The win here isn't "more bells and whistles in JetStream".... it's that locality, overflow, and failover are handled natively by NATS, in the same JetStream config you already run.

A scheduler. A load balancer. A leader-election service. Most "route work to the right place" problems get solved by adding a system. But then you need to maintain and operate that stuff. @NATS_io JetStream consumer priority groups turn that routing into consumer configuration instead.