Qaze

👀👀👀

Another great example of @nats_io powering #edge based #AI platforms.

So many new features that make you more productive working with @nats_io 🔥

Our long-time engineer & NATS wizard Wally rarely gets to experience the "fruits of his labor." But @Rivian's Halloween Mode has been especially fulfilling. 🎃👻 Checkout Wally's Rivian in action this week! Of course, he'd say the real magic happens in the messaging layer!

Tomorrow @nats_io turns 15! We're celebrating with gifts... for you! Here's how it works: 1. Post here on X about why NATS is a great fit for your specific use case. The more details the better! 2. Tag the @nats_io and @synadia accounts in your post 3. We'll message you with a link to choose your NATS hat or shirt! --- The fine print: - some geographies may not be supported by our vendor - quantities are limited, but we'll do our best to reward all good faith posts

NATS 2.12 is here! Love seeing how NATS keeps pushing the boundaries of messaging. Atomic batch publish + delayed scheduling are game-changers for real-world apps. Congrats to the team! 👏👏👏

Bottom line: NATS offers the full spectrum - from lightweight Core NATS patterns (pub/sub, request/reply, queues) to powerful JetStream persistence patterns. Start simple with Core NATS, add persistence when needed.

Stream Sourcing & Mirroring: Create streams that source from other streams or mirror entire streams. Build complex data pipelines with transformation and aggregation across multiple data sources.

Object Stores: Chunked file transfer and storage API. Upload large files efficiently with automatic chunking. Perfect for document management and binary data distribution across your system.

NATS isn't just a fast messaging like any other system - it's a Swiss Army knife of communication patterns. From simple pub/sub to complex streaming workflows, let's explore all the ways NATS can power your distributed systems. 🧵

Key-Value Stores: Built on JetStream streams - Atomic operations on key-value pairs with history tracking. Great for configuration management, feature flags, and shared state between services.

Work Queues: A stream feature where WorkQueuePolicy removes acknowledged messages from the stream. Perfect for job queues where each task should only be processed once across all workers.

Durable vs Ephemeral Consumers: Durable consumers survive restarts and remember their position. Ephemeral consumers exist only while active - perfect for temporary monitoring, event sourcing or debugging scenarios.

JetStream Pull Consumers: Client-controlled consumption with batching. Request exactly how many messages you want, when you want them. Perfect for high-throughput scenarios and backpressure management.

JetStream Streams: Persistent messaging that stores messages for replay. Unlike Core NATS (fire-and-forget), streams capture messages and let consumers process them later, with configurable retention policies.

Queue Groups (Load Balancing): Multiple subscribers, same queue name = automatic load balancing. Messages randomly distributed across group members. Scale up by adding instances, scale down by removing them. Zero config changes needed.

Request-Reply: Synchronous-style communication in an async world. Send a request with a unique reply subject, get responses back. NATS auto-generates _INBOX subjects for seamless RPC-like interactions without the complexity.

Publish-Subscribe (Fan-out): The classic 1:N pattern. Publish once to a subject like orders.created and ALL interested subscribers get the message. Perfect for event broadcasting, notifications, and decoupled architectures.

👉Bottom line: NATS Leaf Nodes are the perfect solution for extending NATS to edge locations, IoT deployments, or any scenario where you need local performance with global connectivity

Scale considerations: If connecting to a cluster, configure ALL seed servers to accept leaf connections. The discovery protocol will handle failover automatically - your leaf nodes stay connected even if individual cluster nodes go down.

Ever wondered how to extend NATS clusters across different networks or edge locations? With NATS Leaf Nodes - a powerful way to bridge local and remote NATS systems! Let's dive in 🧵 #natsio