[Feature]: Change communication direction

[freedbygrace]

Describe the feature you would like to see

One thought I have though is that in order for this to be highly scalable, you will have to construct a proper internal network structure, or for remote hosts, you have to rely on things like Tailscale, Wireguard, etc in order to make all this happen because this appears to use Server initiated communication. So that client has to be reachable. What about clients in remote networks where you do not control the network structure, etc.?

My recommendation would be to use a client-initiated communication so that clients behind other firewalls/NATs would make outbound/reverse connections to the server that could be sitting in the cloud on VPS or self-hosted with reverse proxy etc. The clients would collect and monitor their information, then send it to the server or use something like Centrifugo, RTT, MTT, etc, in order to have like a consistent messaging communication from the agent to the server. Ultimately, the experience would be the same on the server, but the communication plumbing would be different.

This would make clients more secure also, because no ports need to be open on each individual client for server-initiated communication.

Along with that, at some point in the future, servers can be synchronized or function as replicas for load balancing situations!

Describe how you would like to see this feature implemented

[henrygd]

I just want to compliment your work here. I wish every feature request was this detailed!

We have a discussion going on this topic in #51. The current plan is to use NATS, but that's not finalized.

It's the next major feature on my list so it shouldn't be too long. Hopefully by the end of February.

[freedbygrace]

I am glad to contribute! Thank you for making this type of thing a reality and reducing the barrier of entry! I look forward to the update!