Use of the logging NATs service for app messaging


I’m working on a system that may need the ability to bulk cache clear on a set of nginx or varnish servers distributed across several regions. I know this can be done just by restarting them, and using the new machines API is pretty quick.

That being said, I feel like this is pretty heavy handed. I was hoping to have a service run along side in the docker container that could just clear the caches without a machine restart. For receiving the trigger, I was thinking of using NATs. I’ve seen the examples for the NATs cluster (GitHub - fly-apps/nats-cluster: Global messaging for apps that need to talk to each other.), but I also use the log shipper (GitHub - superfly/fly-log-shipper: Ship logs from fly to other providers) for organizational logging. This is also currently using NATs - can other applications utilize this to send messages inside of an org without the added dependency of running our own NATs cluster?

I’m happy to provide more context for the use case as well.


I came here to ask this exact same question!

I tried it out by connecting through wireguard and running nats pub hello "hello", but get a nats: error: nats: Parser Error, so I assume writing to the logs nat server is disabled.