GoSF: Decoupling Services from IP networks with NATS
•
4 likes•396 views
In this talk, we’ll demonstrate how to radically simplify your deployment with NATS, through location transparency, using multiple communication patterns, isolated communication contexts, distributed security, and zero configuration application failover. You’ll learn core NATS features like publish/subscribe, load-balanced queue subscribers, request/response, as well as some of its more recent security features such as securing streams and services with permissions, account isolation and NATS keys (NKEYS, ed25519 based), and decentralized auth via JSON Web Tokens (JWTs) by showing the internals of a decentralized Slack-like demo application.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to GoSF: Decoupling Services from IP networks with NATS
Similar to GoSF: Decoupling Services from IP networks with NATS (20)
Recently uploaded
Recently uploaded (20)
GoSF: Decoupling Services from IP networks with NATS
- 1. Decoupling Services from IP Networks with NATS Messaging Go SF Meetup / July 2019 Waldemar Quevedo / @wallyqs
- 2. @wallyqs #GoSF ● Waldemar Quevedo / @wallyqs ● Software Engineer at Synadia Communications, Inc ● NATS core maintainer (Ruby, Python, Go, K8S) ● Author of Practical NATS (Apress, 2018) About me
- 3. @wallyqs #GoSF Agenda ● Overview of NATS Messaging ● Building secure & decentralized services using NATS v2 ● Demo
- 7. @wallyqs #GoSF NATS is a simple, production proven, cloud-native messaging system.
- 8. @wallyqs #GoSF ICYMI: NATS v2.0 released 🎉
- 9. @wallyqs #GoSF Also repository renamed 🙈 Before: https://github.com/nats-io/gnatsd Now: https://github.com/nats-io/nats-server ⚠
- 10. @wallyqs #GoSF Also repository renamed 😬 Before: https://github.com/nats-io/go-nats Now: https://github.com/nats-io/nats.go ⚠
- 11. @wallyqs #GoSF Now using Go modules 😬🙇
- 12. @wallyqs #GoSF Now using Go modules 😬🙇🤦
- 13. @wallyqs #GoSF Now using Go modules 😬🙇🤦🙏 https://github.com/golang/go/issues/32483
- 14. @wallyqs #GoSF New Docs site (with Dark mode) https://nats-io.github.io/docs/
- 15. @wallyqs #GoSF CNCF Landscape Joined CNCF as an incubation project in 2018 https://landscape.cncf.io
- 16. @wallyqs #GoSF CNCF Landscape Joined CNCF as an incubation project in 2018 https://landscape.cncf.io
- 18. @wallyqs #GoSF Project almost 10 years old...
- 19. @wallyqs #GoSF NATS Origins ● Created by Derek Collison in 2010 for CloudFoundry ● DNA: Simplicity, performance, security, and availability ● TCP/IP based with a very simple plain text protocol | PUB | SUB | UNSUB | CONNECT | INFO | MSG | -ERR | +OK | PING | PONG |
- 20. @wallyqs #GoSF What if all it took to connect all your services was a single URL?
- 22. @wallyqs #GoSF An always available dial-tone
- 23. An always available dial-tone
- 24. An always available dial-tone
- 25. An always available dial-tone
- 26. An always available dial-tone ❌ ❌
- 27. An always available dial-tone ❌ ❌
- 28. @wallyqs #GoSF Core of NATS: 3 Simple Patterns
- 29. @wallyqs #GoSF Messaging Patterns ● Publish/Subscribe (1:N) ● Request/Reply (1:1) ● Load Balanced Queue Subscribers (1:1)
- 30. @wallyqs #GoSF Messaging Patterns ● Publish/Subscribe (Streams) ● Request/Reply (Services) ● Load Balanced Queue Subscribers (Streams or Services)
- 31. @wallyqs #GoSF Publish/Subscribe (1:N) NATS Client SUB foo PUB foo NATS Client NATS Client NATS Client
- 37. @wallyqs #GoSF Request/Response (1:1) PUB help NATS Client SUB help NATS Client NATS Client NATS Client
- 38. @wallyqs #GoSF Request/Response (1:1) PUB help NATS Client First message would be lowest latency response NATS Client NATS Client NATS Client SUB help
- 39. @wallyqs #GoSF Request/Response (1:N) PUB help NATS Client NATS Client NATS Client NATS Client Scatter & Gather multiple replies SUB help
- 40. @wallyqs #GoSF Request/Response (1:N) PUB help NATS Client Scatter & Gather multiple replies NATS Client NATS Client NATS Client SUB help
- 43. @wallyqs #GoSF Load Balanced Queues SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client Randomly distributed
- 44. @wallyqs #GoSF Load Balanced Queues SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client Randomly distributed
- 45. @wallyqs #GoSF Load Balanced Queues SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client Randomly distributed
- 46. @wallyqs #GoSF Load Balanced Queues SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client Randomly distributed
- 47. @wallyqs #GoSF Load Balanced Queues SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client Randomly distributed
- 49. @wallyqs #GoSF Wildcards SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client NATS Client SUB >
- 50. @wallyqs #GoSF Wildcards SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client NATS Client SUB >
- 51. @wallyqs #GoSF Wildcards SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client NATS Client SUB >
- 52. @wallyqs #GoSF Wildcards SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client NATS Client SUB >
- 53. @wallyqs #GoSF Wildcards SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client NATS Client SUB >
- 54. @wallyqs #GoSF Wildcards SUB foo workers PUB foo NATS Client NATS Client NATS Client NATS Client NATS Client SUB >
- 55. @wallyqs #GoSF Wildcards SUB foo.bar workers PUB foo.bar NATS Client NATS Client NATS Client NATS Client SUB > NATS Client SUB foo.*
- 56. @wallyqs #GoSF Wildcards SUB foo.bar workers PUB foo.bar NATS Client NATS Client NATS Client NATS Client SUB > NATS Client SUB foo.*
- 57. @wallyqs #GoSF Wildcards SUB foo.bar workers PUB foo.bar NATS Client NATS Client NATS Client NATS Client SUB > NATS Client SUB foo.*
- 58. @wallyqs #GoSF Wildcards SUB foo.bar workers PUB foo.bar NATS Client NATS Client NATS Client NATS Client SUB > NATS Client SUB foo.*
- 59. @wallyqs #GoSF Wildcards SUB foo.bar workers PUB foo.bar NATS Client NATS Client NATS Client NATS Client SUB > NATS Client SUB foo.*
- 61. @wallyqs #GoSF Delivery modes At most once (Core) ● No guarantee of delivery ● Messages can be lost ● Applications must detect and handle lost messages https://github.com/nats-io/nats-server
- 62. @wallyqs #GoSF Delivery modes At least once (Streaming) ● Ensure message delivery ● Messages are persisted ● Messages may be delivered more than once https://github.com/nats-io/nats-streaming-server
- 63. @wallyqs #GoSF Messages replay with NATS Streaming (STAN)
- 64. @wallyqs #GoSF Message replay with STAN NATS Streaming Client NATS Streaming Server ● A NATS Streaming Server can be attached to the NATS network and provide persistence of messages.
- 65. @wallyqs #GoSF Message replay with STAN
- 66. @wallyqs #GoSF Message replay with STAN
- 67. @wallyqs #GoSF Decentralized Services w/ NATS v2
- 68. @wallyqs #GoSF Classic NATS v1 App Architecture HTTP Server HTTP Server NATS Service NATS Service Load Balancer
- 69. @wallyqs #GoSF No more silos! ● NATS v2 is multitenant ○ (containers but for messaging) ● A NATS user can now exist within an account ○ By default the global account ($G)
- 70. @wallyqs #GoSF Messaging Patterns ● Publish/Subscribe (Streams) ● Request/Reply (Services) ● Load Balanced Queue Subscribers (Streams or Services)
- 75. @wallyqs #GoSF Decentralized auth via JWTs https://api.synadia.io /jwt/v1/accounts/AA OSCON6ID63VZPP AZRHMHKNYLNX7 N4J5UEWVSI64XLR ZXZCYYVBTXG5?de code=true
- 76. @wallyqs #GoSF Classic NATS v1 App Architecture HTTP Server HTTP Server NATS Service NATS Service Load Balancer
- 77. @wallyqs #GoSF Super Clusters with Gateways NATS Service NATS Service NATS Service NATS Service EU West US West
- 78. Super Clusters with Gateways nats://connect.ngs.global:4222
- 82. @wallyqs #GoSF ● To join the demo: docker run -it wallyqs/nats-gosf2019 nats-req chat.req.access user$RANDOM > my.creds chat -creds my.creds https://github.com/connecteverything/oscon2019 Demo: Decentralized Chat App
- 84. @wallyqs #GoSF Thanks! https://natsio.slack.com To join the real NATS Slack: