Intro: NATS
summary
NATS presents itself as a lightweight, Go-based pub/sub system with measured peaks of 18 million messages/sec (single-node) and up to 80 million messages/sec on beefy machines, and separates core NATS (at-most-once) from Stan/Streaming (at-least-once, RAFT-backed). The upcoming v2 adds superclusters, gateways and leaf nodes for multi‑datacenter routing, nKeys and JWT-based auth for decentralized accounts, a Kubernetes operator (v0.5, B2-ready) and a demonstrated supercluster deployable today; v2 ships soon.
AI-written summary · about
chapters (30)
- 0:00Start
- 1:22Agenda
- 2:02About NATS
- 3:30CNCF Landscape
- 4:25Contribution stats
- 6:40Use Cases
- 7:53Messaging Patterns
- 8:30Subjects
- 9:30Request/Response (1:1)
- 9:48Load Balanced Queues
- 10:01Wildcards
- 11:58Performance Decisions
- 12:46Availability
- 14:20Simplicity
- 15:11Auto-Discovery
- 15:50Delivery Modes
- 17:30NATS Server
- 18:15NATS Clients
- 18:33NATS Official Clients
- 18:46NATS Client API: GO
- 19:59Full mesh NATS Cluster
- 20:33NATS Streaming (STAN) N
- 20:45STAN Clients
- 21:14STAN Client API: GO
- 21:58STAN on top of NATS
- 22:40NATS v2
- 26:26Accounts
- 26:39Streams & Services
- 27:53NKeys and JWTS
- 29:40NATS Operator
related talks
29mA New Generation of NATS
40mThe Zen of High Performance Messaging with NATS
21mNATS: A high-performance messaging system for communication between services
37mConnect All the Things! Using NATS To Simplify Communication Everywhere
34mState of NATS: Core, Persistence, & Materialized Views
35mThe NATS Stack - Libraries Extensions and the Execution Engine
25mBeyond Kafka: Leveraging Event-Driven Architectures with Go and NATS JetStream
25mInside the Decision: Why Groww Chose NATS Over WebSockets