The ability for the node-sdk to be resilient to unavailable nodes is something that would be common to all users of the sdk. For example
When listening for chaincode events, either listen on all eventSource peers and de-duplicate or ensure that before a submission to the orderer that connection to an eventSource exists for chaincode events
When querying ledgers or chaincode, you only need to send the query to a single peer (unless really want to do a peer response comparison), but if that peer is down, try another peer in the same organisation and if all the same org peers, fail start trying peers in other organisations.
The ability to define more than 1 CA in a connection profile for an organisation and then fallover to another if the first one responds with an error
There are probably other scenarios to be considered, so would be good to get other ideas into this JIRA. I am not proposing that the node-sdk changes it's behaviour or current apis. I think a base capability in the node-sdk is vital but rather a new api that provides these more complex capabilities
The ability for the node-sdk to be resilient to unavailable nodes is something that would be common to all users of the sdk. For example
When listening for chaincode events, either listen on all eventSource peers and de-duplicate or ensure that before a submission to the orderer that connection to an eventSource exists for chaincode events
When querying ledgers or chaincode, you only need to send the query to a single peer (unless really want to do a peer response comparison), but if that peer is down, try another peer in the same organisation and if all the same org peers, fail start trying peers in other organisations.
The ability to define more than 1 CA in a connection profile for an organisation and then fallover to another if the first one responds with an error
https://jira.hyperledger.org/browse/FAB-5565 for the orderer
There are probably other scenarios to be considered, so would be good to get other ideas into this JIRA. I am not proposing that the node-sdk changes it's behaviour or current apis. I think a base capability in the node-sdk is vital but rather a new api that provides these more complex capabilities