After defining all the previous steps, we will go on to describe our blockchain architecture.
The architecture for blockchain includes elements like infrastructure, software and hardware.
As per your business requirements, you need to see whether the blockchain solution would be solely
based on cloud premises, native premises, or is it going to be a hybrid model of both?
Blockchain architecture is essential for your solution because it will define how other applications
and services will connect to your blockchain application or project.
Blockchain architecture will also include your authorization and permission policies.
For example, you might be doing a solution for education industry where you store the credentials of
students over the blockchain.
You can set up a permission blockchain where the students only have the read permissions for the credentials
and on the other hand, the universities have the read and write permissions for the student credentials.
In future, employers can connect to this blockchain and they might also have read permissions, making
sure student credentials are immutably stored over the blockchain.
Blockchain architectures can be designed as per the permissions and interaction capabilities required
for the solution.
Once you have finalized the use case, consensus algorithm platform and also design the architecture,
the next step required is to finalize the design of blockchain instance.