Using NATS
summary
Form3 replaces SNS/SQS fanout with NATS and JetStream to cut tail latency and run lightweight event streaming in private data centers, processing 1M+ messages/day since March 2020; code snippets are small Go clients using NATS clients, push and pull consumers for rate control, and JetStream gives persistence, at-least-once delivery and deduplication window 2m by default; production setup recommends clustered JetStream (about 3–5 servers) and reports noticeable performance improvement versus 50–500ms SQS delivery, though exact metrics vary by topology.
AI-written summary · about
chapters (13)
- 0:00Start
- 7:25Nas Fundamental Concepts
- 8:22Messaging Patterns
- 10:49Request and Reply Pattern
- 11:43Wild Cards
- 16:29Start the Nat Server
- 17:32Subscribers in Action
- 20:27Jet Stream
- 26:44Configuration File
- 31:59Push Consumer
- 35:25Out-of-the-Box Clustering
- 39:21Message Duplication
- 39:55Message Replay
related talks
17mNATS: The Challenger to Kafka's Messaging Throne
21mNATS v2.2: The JetStream Release
38mNATS Intro
44mNATS Deep Dive
28mKeynote: The State of NATS as a Reactive Substrate
01h 34mDeploy Secure and Scalable Service...
33mNATS: The Cloud-Native Challenger to Kafka's Messaging Throne
51mBuilding high-performance event-driven systems using NATS
