Introduction to NATS

Demo in github repository : https://github.com/rubiagatra/intro-nats

Transcript

1. Introduction to NATS: A high-performance messaging system as a solution for communication between services DONI RUBIAGATRA kumparan
2. About me • Doni Rubiagatra, @rubiagatra • Bachelor of Mathematics @ ITS Surabaya • Software Engineer kumparan
3. A Mouthful Title eh?
4. So is Software Nowadays
5. Imagine
6. comment-service notification-service
7. comment-service notification-service
8. comment-service notification-service
9. comment-service notification-service messaging-system
10. comment-service notification-service messaging-system
11. The Drawback
15. Features
19. Messaging Pattern
20. • Publish / Subscribe • Load Balanced Queue Subscribers • Request / Reply
21. Subject
22. • Simple subject: kum • Hierarchically Tokenized: kum.foo • Wildcard subscriptions kum.* matches kum.foo and kum.bah. kum.*.bar matches kum.a.bar and kum.b.bar. foo.> matches any of the above > matches everything in NATS A subject is simply a string representing an interest in data.
23. CLIENT CLIENT PUB kum SUB kum
24. CLIENT CLIENT PUB kum SUB kum CLIENT CLIENT
25. CLIENT CLIENT PUB kum SUB kum worker CLIENT CLIENT Randomly Distributed
26. CLIENT CLIENT PUB kum SUB kum worker CLIENT CLIENT Randomly Distributed
27. CLIENT CLIENT PUB kum SUB kum worker CLIENT CLIENT Randomly Distributed
28. CLIENT CLIENT PUB kum.bah SUB kum.bah worker CLIENT CLIENT CLIENT SUB >
29. CLIENT CLIENT PUB kum.bah SUB kum.bah worker CLIENT CLIENT CLIENT SUB >
30. CLIENT CLIENT PUB kum.bah SUB kum.bah worker CLIENT CLIENT CLIENT SUB >
31. CLIENT CLIENT PUB kum.bah SUB kum.bah worker CLIENT CLIENT CLIENT SUB > CLIENT SUB kum.*
32. CLIENT CLIENT PUB kum.bah SUB kum.bah worker CLIENT CLIENT CLIENT SUB > CLIENT SUB kum.*
33. CLIENT CLIENT PUB kum.bah SUB kum.bah worker CLIENT CLIENT CLIENT SUB > CLIENT SUB kum.*
34. Simplicity
35. • Single binary • 7.8 MB docker image with no external dependencies • “Text-based” protocol with just a handful of verbs • Low Configuration Clients only need a url and credentials Servers auto-discover You can share configuration files amongst servers • Simple and Straightforward API
36. Delivery Modes
37. • At most once (Core) No guarantee of delivery - messages can be lost - applications must detect and handle lost messages • At least once (Streaming) A message will always be delivered, but in certain cases may be delivered more than once NATS Support two delivery modes
39. A Little bit demo https://github.com/rubiagatra/intro-nats
40. ANIME- SERVICE SEARCH- SERVICE CLIENT
41. • Introduction to NATS - Video • https://nats.io/ • Practical NATS From Beginner to Pro - Waldemar Quevedo References & Check this one out
42. kum.pr/join