NATS.fm S2EP1: Welcoming in 2024 with a bang

1. Distributed Message TracingGain full visibility into message paths across complex NATS topologies — including clusters, gateways, leaf nodes, account boundaries, and subject mappings.- Activated via a NATS-Trace header and supported directly in the CLI (nats trace [subject]).- Supports dry runs: trace a message’s route without delivering it, ideal for debugging or verification.- Useful for both operators and developers to understand and verify message flow behavior.2. Per-Message TTL (Time-To-Live)Set expiration per message with the NATS-TTL header — allowing messages to age out individually, regardless of stream-level retention settings.- TTLs are optional and per-message: not all messages need one, and TTL values can differ.- Backed by an efficient timed hash wheel structure to minimize memory use.- Major benefits for KV buckets — TTL-based deletion markers reduce storage and avoid manual compaction.3. Consumer Priority GroupsA new mechanism for pull-based load balancing and resilience:- Introduces overflow rules: clients can take over message delivery if primary clients are overwhelmed, using thresholds for pending messages or ACKs.- Pinning: designate a single client to receive all messages until it fails, enabling failover patterns.- One priority group per consumer in this release, designed to expand in the future.- Enables simpler, cost-effective cross-region and zone-aware delivery strategies.4. Multi-Message Get (Batch Get)Efficient, stateless retrieval of multiple messages from a stream — without creating consumers.- Supports multiple subject filters, time/sequence bounds, and returns data in sequence order.- Ideal for querying the latest messages, previewing stream data, or powering internal state lookups.- Foundational for upcoming KV/Object Store improvements and future batch operations.5. Consumer PauseTemporarily halt message delivery without tearing down the consumer or triggering client-side errors.- Works with both push and pull consumers.- Specify a pause_until deadline in the config — message flow resumes automatically afterward.- Heartbeats continue, so clients stay connected and unaware of the pause.- Valuable for maintenance, orchestration, or preventing unwanted consumption during deployments.

Tomasz Pietrek and David Gee are back to discuss Orbit: the NATS client extensions!You can find the Orbit libraries below:https://github.com/synadia-io/orbit.gohttps://github.com/synadia-io/orbit.jshttps://github.com/synadia-io/orbit.javahttps://github.com/synadia-io/orbit.rsEnjoy.

Tomasz Pietrek, Maurice van Veen and David Gee kick off season 3 and we're off the blocks with a back to basics episode! We chat core NATS, the basics of a connection and the pub-sub turtles (all the way down)! Season 2 was spectacularly short (one episode) and so let's kick off S3 for 2025 with this early December special! Enjoy.

Welcome to season two of NATS.fm! We start off this season by talking about Synadia's RethinkConn 2024 and the excitement around some of the new up and coming NATS Execution Engine, Synadia Cloud, the NATS ambassador programme and more! If you're interested in NEX, you can find more here: https://nats.io/blog/introducing_nex/For the RethinkConn 2024 videos: https://www.synadia.com/blog/rethinkconn-2024 Want to try out NATS in the cloud for free?Head over to https://cloud.synadia.com

NATS provides incredibly powerful usage patterns and one of the most fundamental is streams and consumers. This pairing is a super power and can solve many challenges in the most simplest way. We cover the bare fundamentals of NATS streams and how to consume data from them with some model use cases to help the exploration. Want to feel more confident about how to embrace data streams? Take a listen as we go back to basics. --- If you like this video, be sure to hit like and subscribe! Want to suggest a topic? Find us on Twitter (https://twitter.com/nats_io), LinkedIn (https://www.linkedin.com/showcase/nat..., or Slack (https://slack.nats.io)! Here are some useful links for NATS! - Website - https://nats.io - Examples - https://natsbyexample.com - Docs - https://docs.nats.io The home of the NATS team: https://synadia.com

From self-driving cars, to intelligent toasters, this resurgence of artificial intelligence is here to stay. In this episode, we talk about how NATS.io could be the perfect system to connect your AI, ML and DL systems to your business software from the tiniest of systems and machines, across the edge(s) and back to the data center. --- If you like this video, be sure to hit like and subscribe! Want to suggest a topic? Find us on Twitter (https://twitter.com/nats_io), LinkedIn (https://www.linkedin.com/showcase/nat..., or Slack (https://slack.nats.io)! Here are some useful links for NATS! - Website - https://nats.io - Examples - https://natsbyexample.com - Docs - https://docs.nats.io The home of the NATS team: https://synadia.com

Now that we have v2.10 of the nats-server released, it's time to discuss what we can do with NATS. We start by discussing patterns that we can easily achieve with the KV store. Enjoy! --- If you like this video, be sure to hit like and subscribe! Want to suggest a topic? Find us on Twitter (https://twitter.com/nats_io), LinkedIn (https://www.linkedin.com/showcase/nat..., or Slack (https://slack.nats.io)! Here are some useful links for NATS! - Website - https://nats.io - Examples - https://natsbyexample.com - Docs - https://docs.nats.io The home of the NATS team: https://synadia.com

It's here!!! Server 2.10 of the nats-server has been released, and with it, a whole swathe of new features and capabilities. Byron sits down with Neil Twigg and Tomasz Pietrek to talk about what's new and their journey with the nats-server and clients from 2.9 to 2.10. Want to suggest a topic? Find us on Twitter (⁠@nats_io⁠) or our community Slack > ⁠https://slack.nats.io ⁠ Useful Links⁠https://examples.nats.io⁠⁠https://docs.nats.io ⁠The home of the NATS team: ⁠https://synadia.com

Welcome to episode 5 and our first episode with a special guest! Byron & Dave chat with Tomasz Pietrek, the NATS client team lead engineer on the powerful client libraries. We dig in to JetStream simplification, the KV & Object Store and the Micro Services API. Buckle in for our longest episode yet! Want to suggest a topic? Find us on Twitter (⁠@nats_io⁠) or our community Slack > ⁠https://slack.nats.io⁠ Useful Links ⁠https://examples.nats.io⁠ ⁠https://docs.nats.io⁠ The home of the NATS team: ⁠https://synadia.com

Welcome to episode 4, the last chat about service meshes (for now)! In EP03, David got stuck, rambling about service and function chaining and Byron gives him a chance to redeem himself and explain properly. The outcome is a hugely simplified approach to service mesh deployment and the narrowing of technical complexity and an increase in capabilities. We go through the most popular features that you're likely to deploy and how using NATS.io, Byron would approach the requirements. Want to suggest a topic? Find us on Twitter (⁠@nats_io⁠) or our community Slack > ⁠https://slack.nats.io⁠ Here are some useful links for NATS! ⁠https://examples.nats.io⁠ ⁠https://docs.nats.io⁠ The home of the NATS team: ⁠https://synadia.com