Qaze retweeted
👉 New blog post: NATS 2.14 (RC 1) Fast-Ingest Batch Publishing
qaze.app/blog/nats-fast-inge… #nats #natsio #jetstream
Qaze retweeted
I’m with you on this, I’ve been doing something similar to gas town but using Nats as the lattice much like wasmcloud
Cloud native distributed background agents
Teams should be building army of agents soon
github.com/cloudshipai/stati…
So many new features that make you more productive working with @nats_io 🔥
Qaze 1.4 is out 🚀
📝 Stream & KV Forms - create & edit Streams/KVs + config diff view
🔍 Stream Message History + Filters
🔗 Stream & KV Relations - visual graph of mirrors, sources & republish targets
📊 Real-time Server Monitoring (Top) - dashboard with sparklines
⏸️ Pause/Resume Consumers - manage all consumers at once or individually
🌐 Redesigned Server Graph - clearer topology view with node focus
🗑️ Bulk Delete - multi-select items directly from the navigation
#natsio #nats #qaze
Qaze retweeted
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!
Qaze retweeted
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
Qaze retweeted
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! 👏👏👏
🚀 NATS Server 2.12 is officially here!
More performance. More resilience. More possibilities.
✨ Atomic batch publish - no more partial commits
⏰ Delayed message scheduling - schedule messages for later consumption
🔢 Distributed counters with unlimited size (big.Int support!)
🎯 Prioritized pull consumer policy for fast failover
🔄 Mirror promotion for disaster recovery
🛡️ Offline asset protection during downgrades
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.
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.
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.