Blockchain is the buzz word today and would remain for sometime.
Before we decide to re-design an application or a system as Block-chain we should follow some guidelines.
When BLOCK CHAIN can be beneficial for you?
1. If your application or business has multiple parties involved and smart contracts will be beneficial.
2. If you are ok to expose the business rules on an open ledger.
3. If it is not an instant i.e. real time transaction expectation ( projects like instant message etc. are not for block chain due to the sync on nodes. It won't be real time anymore.
4. If you do not want to use third parties to avoid some costs.
Now, in cases where you an your corporate organization, where you want to have block chain, but not open to all and limited parties.
KEY POINT
Decide the multiple parties involved. They will become your clients e.g. lets say ETH clients.
If your users are end customers, and you do not want to expose them to real ETH address/wallet.
You might need to have a hybrid architecture.
So your architecuture on AWS with Private Subnets ( for ETH clients) and Public Subnet ( for APIs) might look like as below
The components which you might use for creating a block chain would look most likely like the below.
Microsoft, AWS and Google are aggressively into block chain framework.
Details will architecture and video to design applications will be present on my next blogs soon.
Before we decide to re-design an application or a system as Block-chain we should follow some guidelines.
When BLOCK CHAIN can be beneficial for you?
1. If your application or business has multiple parties involved and smart contracts will be beneficial.
2. If you are ok to expose the business rules on an open ledger.
3. If it is not an instant i.e. real time transaction expectation ( projects like instant message etc. are not for block chain due to the sync on nodes. It won't be real time anymore.
4. If you do not want to use third parties to avoid some costs.
Now, in cases where you an your corporate organization, where you want to have block chain, but not open to all and limited parties.
KEY POINT
Decide the multiple parties involved. They will become your clients e.g. lets say ETH clients.
If your users are end customers, and you do not want to expose them to real ETH address/wallet.
You might need to have a hybrid architecture.
So your architecuture on AWS with Private Subnets ( for ETH clients) and Public Subnet ( for APIs) might look like as below
The components which you might use for creating a block chain would look most likely like the below.
Microsoft, AWS and Google are aggressively into block chain framework.
Details will architecture and video to design applications will be present on my next blogs soon.
Wonderful article preserve accomplishes putting up. It's not at all a moment my spouse and i. electronic. Real-time financial transaction hopes assignments similar to instantaneous communication Heroku vs AWS and many others. are certainly not pertaining to stop archipelago due to sync in nodes. It certainly can't always be real-time ever again.
ReplyDelete