EP08: AI at the Edge(s) with NATS.io

From self-driving cars, to intelligent toasters, this resurgence of artificial intelligence is here to stay. In this episode, we talk about how NATS.io could be the perfect system to connect your AI, ML and DL systems to your business software from the tiniest of systems and machines, across the edge(s) and back to the data center.
---
If you like this video, be sure to hit like and subscribe!
Want to suggest a topic? Find us on Twitter ( / nats_io , LinkedIn ( / nat.. , or Slack (slack.nats.io)!
Here are some useful links for NATS!
- Website - nats.io
- Examples - natsbyexample.com
- Docs - docs.nats.io
The home of the NATS team: synadia.com

[@siva710]

Nats server team is doing an excellent job. But the amount of issues recently opened in the github makes our team worried about the stability of our projects. After a long waiting time of 3.10 release, we are hesitant about upgrade. We had plans to replace existing dependencies with Nats features. But having Nats as a major dependency scares us when we look at the open issues after 3.10 release. But no question about its performance and the simplicity it offers to the overall architecture. Keep up the good job as always.❤

[@SynadiaCommunications]

Hey @siva710. We appreciate the kind words and understand the perception of lots of open issues. The team has been addressing the high priority and reproducible ones quite quickly. If there are specific concerns you have or open issues that impact your use case, please reach out on those issues or on the NATS Slack.

[@JohnMcclaned]

Can you do a video on the limitations of NATS? Is there a point where everything falls apart? What's the throughput? How reliable is it? Thanks

[@SynadiaCommunications]

Thanks for the comment! We'll take it to the drawing board and plan an episode!

[@jaysistar2711]

I have some questions about JetStream and NATS servers that will be disconnected some of the time, as well as how to make JetStream keep certian streams on certian nodes. The documentation that I've seen is a bit sparse. What's a good resource?

[@SynadiaCommunications]

Good set of questions. The simpler question of the two is placement of nodes on specific servers. This is done using cluster and placement tags: docs.nats.io/nats-concepts/jetstream/streams#placement. Depending on your topology design, servers may be part of a named cluster and have tags indicating some attribute like availability zone. When creating a stream you can choose and explicit cluster and/or set of tags that the stream replicas must be placed on.
For the other question about "disconnected some of the time", as a general statement, NATS connections (be it client, cluster, gateway, or leafnode) will continuously attempt to reconnect when disconnects occur. I suspect you may be asking more about the behavior of stream replication when those disconnects happen. There are some nuances to consider with that depending on the stream configuration so feel free reach in NATS slack (slack.nats.io).