Achieve MASSIVE Scale with NATS Clustering | Rethink Connectivity Episode 4

Learn how to cluster together multiple NATS servers to scale up how your microservices communicate and how data flows through your applications.
NATS is a connective technology powering modern distributed systems, unifying Cloud, On-Premise, Edge, and IoT.
Join the NATS Community on Slack: slack.nats.io
Learn More about NATS at docs.nats.io/
#devops #distributedsystems #natsio

[@MarkusEicher70]

Very interesting and helpful intro to NATS clustering. So happy to have found this channel. Thanks Jeremy.

[@delaneygillilan]

Great stuff, I'd really like to see you cover a more concrete example of the decentralized JWT work flow!

[@SynadiaCommunications]

Agreed. I things introducing people to the JWT workflow will definitely be a topic we will cover soon

[@minamohammadi1093]

Thanks for your great videos
It was wonderful
move on

[@tyortyo]

Oo man, thank you very much!!

[@Oderwat]

The one thing I think is missing from most cluster examples I saw is, that you do not want to shut down and restart the cluster to change the servers' config. Reloading the server configs is possible, but this will not use the server name from the command line and then abort the reload. So, you can't share one config like in this example if you want to be able to reload the servers. I need to be more experienced to know if running the actual cluster will need reloads of the configs, though. My current experiments involve plenty of changes in the configuration (like adding and removing accounts and users).

[@SynadiaCommunications]

I think this is a great idea for another episode! NATS supports hot reloading of server configs for most fields

[@Mo.Faried]

A great informative tutorial, but I have to ask, which terminal client are you using? Is it ITerm2?

[@michaelgrauvogl689]

Great. Thank you!

[@silversword411]

I'm trying to understand nats and websockets...keep the app going.

[@pablovicentico]

Awesome!

[@trailerhaul8200]

Thanks

[@anirbankundu2002]

Would love to see how to setup cluster with account that uses user jwt and nkey instead of using the user/password combination that you showed. I'm getting auth errors even after setting the correct context and the server running with the operator resolver (and jetstream).
$ nats server ping
nats: error: nats: Authorization Violation

[@sacaelcod]

Ufffff no por que me exitan estás cosas

[@SynadiaCommunications]

Glad you enjoyed it