I have worked through the examples and have read all the documentation. In my application I am monitoring a machine which has e.g. 60 copies of a particular function. This is all processed through a micro with a binary coded message. I have the binary unpacked and written a Go struct based model over NATS. Many of the data types are slices sized to the machine e.g. 60 but it could be 30 for another machine. The operating status of the machine is to be observed in a browser or mobile client so the slices will ultimately be updated across the network to the clients. I have no need to individually address any particular unit out of the 60 units in the slice except on the client for display purposes. The updates will come in bulk form the micro updating the entire slice by replacement and sending resgate an update notice.
So in looking at resgate and the go-res server application I could probably work my problem by making the model look like a message with a JSON encoded string as the payload. The client could then simply unpack and display. Since resgate won’t need to update individual items inside the slice and in one place the slice contains a 4 element model would I be right in thinking this would solve my problem.
I have also considered that resgate might be too big a hammer for what I am doing. I however like the update function. There will not be very many clients connected but what you have done also solves a lot of problems for me since this is a new application I have started in Go I have a lot of latitude for selection.
I think NATS is the best message bus for what I am doing, fast, simple and solid as a rock.
Thanks for any thoughts,