Currently our NATS streaming client does multiple things. On requester node side. it is used as a consumer of log messages coming via NATS and on compute node it acts as write, where it reads logs from appropriate execution engines and puts them as messages on NATS subject.
With this change we go with single responsibility per client and split the client into ConsumerClient and ProducerClient. This makes it easy and each client has single responsibility.
With this change we also add the logic of producer client sending heart beats to consumer client on a heart beat request subject, when a connection is made.
What is this change about ?
Currently our NATS streaming client does multiple things. On requester node side. it is used as a consumer of log messages coming via NATS and on compute node it acts as write, where it reads logs from appropriate execution engines and puts them as messages on NATS subject.
With this change we go with single responsibility per client and split the client into
ConsumerClientandProducerClient. This makes it easy and each client has single responsibility.With this change we also add the logic of producer client sending heart beats to consumer client on a heart beat request subject, when a connection is made.