Build Distributed Systems with NATS.io

Transcript

1. Build Distributed Systems with NATS
2. What is Distributed Systems ? A distributed system is a group of computers working together as to appear as a single computer to the end-user.
3. Benefits of Distributed Systems • Performance • Fault Tolerance
4. Challenges • Partial Failure • Hard to debug / trace
5. Distributed System Communication • Synchronous ◦ REST, RPC • Asynchronous ◦ Kafka, RabbitMQ, Amazon SNS
6. Synchronous Communication
7. Implementation of Synchronous Communication
8. Asynchronous Communication
9. What is NATS ? https://nats.io NATS.io is a simple, secure and high performance open source messaging system for cloud native applications, IoT messaging, and microservices architectures.
10. NATS Creator Created By Derek Collison (https://twitter.com/derekcollison) • Founder & CEO Synadia • Former Founder & CEO Apcera • Creator of CloudFoundry • Google Developer APIs and JS CDN • TIBCO Messaging
11. NATS Users
12. NATS Features • Easy to use for developers and operators • High-Performance • Always on and available • Extremely lightweight • At Most Once and At Least Once Delivery • Support for Observable and Scalable Services and Event/Data Streams • Client support for over 30 different programming languages • Cloud Native, a CNCF project with Kubernetes and Prometheus integrations
13. NATS Benchmark
14. NATS Use cases • Cloud Messaging ◦ Services (microservices, service mesh) ◦ Event/Data Streaming (observability, analytics, ML/AI) • Command and Control ◦ IoT and Edge ◦ Telemetry / Sensor Data / Command and Control • Augmenting or Replacing Legacy Messaging Systems
15. Messaging Pattern • Publish-Subscribe • Queueing • Request-Reply
16. Components of Messaging Architecture • Message: Messages are the unit of data exchange. A payload, which is used for exchanging the data between applications. • Subject: Subject specifies the destination of messages. • Producer: Producers send messages to the NATS server. • Consumer: Consumers receive messages from the NATS server. • Messaging Server: NATS Server distributes the messages from producers to consumers.
17. Implementation of Asynchronous Communication
18. NATS Problem NATS offers an at most once quality of service. If a subscriber is not listening on the subject (no subject match), or is not active when the message is sent, the message is not received. This is the same level of guarantee that TCP/IP provides. By default, NATS is a fire-and-forget messaging system
19. Two Generals’ problem
20. Solution NATS Streaming • Message/event persistence • At-Least-Once Delivery model, giving reliable message delivery • Rate limiting • Replay/Restart • Last Value Semantics
21. Subscription Types • Regular • Durable • Queue Group • Redelivery
22. Implementation
23. NATS Conclusion • Simple • No dependency • Optional persistence • Lightweight; 16MB docker image • Lack of official GUI
24. Reference https://nats.io/ https://bravenewgeek.com/dissecting-message-queues/ https://hub.docker.com/_/nats https://hub.docker.com/_/nats-streaming https://en.wikipedia.org/wiki/Two_Generals%27_Problem