[DOCS] Best practices to design high transaction volume dApps on FLOW blockchain

Issue to be solved

This issue is focused on writing some best practices documentation for the dApps developer who wants to build load-centric dApps.

This documentation should cover the best practices around the following -

• Transaction Queueing process
• Batch Transaction submission
• RPC node infrastructure.
• How to do Airdrop in an efficient manner

Suggest A Solution

Some of the Highlights of the documentation -

• Load-centric dApps, Always create the transaction queuing system instead of blindly submitting transactions on demand. It depends on how dApp developers decide which transactions need to be submitted right away and which can be batched together with other transactions to increase efficiency.

• It is recommended to use batch-style transactions if one operation needs to perform on many users around the same time (approximately). It will save the dApp developers from hitting the throttling limit of the RPC nodes and save a couple of bugs in fees as well.

• If dApps doing Airdrop to mass people then it is recommended to have pull style mechanism instead of push style, which means dApps developers can build a smart contract where they can add the Merkle root build using the entitled addresses and their allocation so they can claim as per there convenience by providing Merkle proof. Or if the list of addresses is not pre-known then at least create the batches of the addresses to whom they want to push the token in a single transaction.

What are you currently working on that this is blocking?

No response