Thank you for your amazing article. Please keep it up. I have one question. Can you explain more about using proxy chaincodes to to cache transactions?
The idea of the cache is to aggregate incoming transactions to the SDK in a batch of transactions (let’s say 10 txs per batch), and send the batch in a single transaction to the peer. Then the chaincode has to be implemented so that it understands batches, and is able to extract the operations of each transaction of the batch.
I may share an example in future posts if you find it interesting.
I would like to understand the following sentence as well: "we can use proxy contracts to cache transactions and kill MVCC conflicts early so they don’t significantly harm the performance of our network." Can you shed me some light on that?
Thank you for your amazing article. Please keep it up. I have one question. Can you explain more about using proxy chaincodes to to cache transactions?
I really appreciate your kind words, Phuwanai.
The idea of the cache is to aggregate incoming transactions to the SDK in a batch of transactions (let’s say 10 txs per batch), and send the batch in a single transaction to the peer. Then the chaincode has to be implemented so that it understands batches, and is able to extract the operations of each transaction of the batch.
I may share an example in future posts if you find it interesting.
I would like to understand the following sentence as well: "we can use proxy contracts to cache transactions and kill MVCC conflicts early so they don’t significantly harm the performance of our network." Can you shed me some light on that?
Yeah, I'm interested to learn more. Can't wait for your new Fabric articles.