Revisit client module for the per route connection pooling in config in cluster/load balance/discovery environment. about light-4j HOT 1 CLOSED

The issue is resolved by upgrading the client to Http2Client so that connection pooling is not necessary as HTTP 2.0 protocol supports multiplex. The user have two options in term of cache connection:

• If you client will be calling service very frequently, then get the connection info from cluster and create a connection and cache it and reuse it. However, the cached connection might be disconnected from the server side(server down etc.) you need to check the connection state before using it. Follow these tutorial to see how it is used.

https://networknt.github.io/light-rest-4j/tutorial/ms-chain/
https://networknt.github.io/light-rest-4j/tutorial/discovery/

Also there is an example client here.

https://github.com/networknt/light-example-4j/tree/master/client

• The other option is to create a new connection for each request and close the connection after the request. This pattern is suitable for infrequent calls to services as it doesn't make sense to hold the resource. Take a look at the example client to see how this is done.

https://github.com/networknt/light-example-4j/tree/master/client

from light-4j.