Read/write batching

[bestbeforetoday]

Fabric v3.1.0 introduced a new performance optimization that allows ledger reads and writes to be performed in batches. This feature is described in the Peer to Chaincode Communication Optimization RFC.

fabric-chaincode-go provides a reference implementation of this functionality, which should be replicated by the Node chaincode libraries.

Implementation is composed of these component parts:

• Configuration of batching based on peer capabilities when a connection is established
• Modifications to PutState (and PutPrivateData) API functions
• An accompanying WriteBatch implementation to collect batched writes.
• Modification of handleInit and handleTransaction to ensure that batched writes are sent at the end of a client invocation
• New Stub API functions:
  • StartWriteBatch
  • FinishWriteBatch
  • GetMultipleStates
  • GetMultiplePrivateData

[ArunRawat404]

@bestbeforetoday I would love to work on this, As you said in fabric-chaincode-java will start by implementation of New Stub API functions.

[Rishabhp68]

Hi,
I’m a senior developer from Oracle’s Blockchain Platform team, and we’re really looking forward to this feature for our Node.js chaincodes. Do you have any updates on when it might become available?

[bestbeforetoday]

PR #454 has not had any update since I reviewed it in May so it does not look like anyone is actively working on this feature right now. Any contributions — either to get the current PR over the finish line or to progress the implementation further — are of course very welcome.

[Vineet1101]

hey @bestbeforetoday I would like to work on this issue

[bestbeforetoday]

@Vineet1101 Great, please go ahead. I would suggest delivering in small increments. Even just delivering the new API with its fallback behaviour where no batching is done as a first step. As you build real batching behaviour, some accompanying tests will be necessary.

[Vineet1101]

@bestbeforetoday sure working on it