NATS Intro
summary
NATS is a single‑binary, cloud‑native messaging system focused on extreme performance and simplicity with built‑in clustering and auto discovery so clients learn topology and auto reconnect. Core NATS offers publish/subscribe request‑reply and queue groups with at‑most‑once core delivery and achieves 18 million messages/sec (128 byte payload) and higher with multiple streams. NATS Streaming layers at‑least‑once streaming guarantees, durable subscribers, replay by time or sequence, last‑value cache, rate matching, storage options and Raft‑based HA. Security includes TLS token auth and a Prometheus exporter for monitoring.
AI-written summary · about
chapters (25)
- 0:00Start
- 0:14What is messaging?
- 0:42Why does CNCF need messaging?
- 1:29What is NATS?
- 2:03History
- 2:44Overview
- 3:15Use Cases
- 3:51Users and Adopters
- 4:38Contribution Statistics
- 5:07Messaging Patterns
- 6:56Performance
- 9:10Simplicity Continued
- 10:04Simplicity (Go API)
- 10:34Simplicity (Java API)
- 11:01Security
- 12:33Availability
- 13:48Clustering
- 14:43Resilience
- 16:22NATS Delivery Modes
- 16:39NATS Streaming
- 18:25Monitoring NATS Servers
- 18:44Monitoring Data
- 19:06NATS and Prometheus
- 19:20NATS / Prometheus / Grafana
- 20:29Contributing
related talks
17mNATS: The Challenger to Kafka's Messaging Throne
33mNATS: The Cloud-Native Challenger to Kafka's Messaging Throne
28mKeynote: The State of NATS as a Reactive Substrate
51mBuilding high-performance event-driven systems using NATS
01h 34mDeploy Secure and Scalable Service...
21mKeynote: NATS: Past, Present and the Future
21mNATS v2.2: The JetStream Release
44mUsing NATS