Best way to handle connection object in NATS?

[YashasAnand]

Is it better to create a long lived connection instance to the NATS broker, or ignore creating the connection as internally publish method is creating connection.

Also in case of consumer, does the library internally handle connection to broker if its not connected already?

Am i getting a performance improvement if i create a long lived connection to broker or is it actually degrading my performance by consuming memory ?

[mtmk]

Yes, typically you should create a connection once as a singleton and use the same object until your application exists. Library internally maintains the connection, reconnects after connection is lost and maintains subscriptions and consume calls.

[YashasAnand]

@mtmk , thank you for your response, I have observed that if connection is not created as a singleton, any messages published to stream will internally open a connection, publish the messages & immediately close.

As per your above comment, you say the client tries to reconnect the same connection when new messages published..
With respect to performance, is it is better to have a singleton instance than use the internal connect-reconnect mechanism?

[mtmk]

that's correct. you'd want the connection to be a singleton so it's established and kept alive internally (by reconnecting when needed)

[YashasAnand]

Thanks again @mtmk !!