So as you have seen with this conceptual view till now that we have segregated different functionalities
which are part of our enterprise systems.
We have segregated the identification managers, the internal systems integration module, blockchain
module and application module.
It could be that you have a team of architect who can take up one single module and build up the whole
conceptual view for those single modules, as we have shown with the Identification Manager, Internal
Systems and Integration Module two.
Another important part of your enterprise blockchain system is the blockchain module, which is going
to be integrated with your legacy systems or new applications are going to be built with that.
We have already gone through different kinds of internal architecture which can be hosted with your
blockchain module.
All those internal architectures can be part of your blockchain module, and this blockchain module
is heavily influenced by the blockchain platform you are going to use.
If you are using a platform like Hyperledger Fabric, you might enable channel services with your blockchain
module.
If you are using a platform like Bitcoin, then you might not have identity management services with
that.
Similarly, if you are using your code module, then you might have to use the point to point ledger
based system with your blockchain module.
So these blockchain modules are going to be based as per the platform you have utilized with your projects.
If you are creating the blockchain by yourself, then this blockchain module will be influenced by the
technical and business decisions which you have taken and factorized into creation of your blockchain
module.
You might have a requirement for a membership service provider and on the other hand you might not require
cryptocurrencies or native assets with your blockchain module.
So all those different factors which define your whole architecture will be catered with your blockchain
module Coming to the definition for the blockchain module, a typical blockchain module will compose
of all the different technical components and business components which we have discussed till now.
Different platforms takes up different shapes with the blockchain module, a generalized module for
a blockchain can hold data block schema chain structure, merkle tree, cryptographic protocol, hash,
function, hash table and across different platforms will focus on different kinds of principles.
If we use Ethereum based blockchain, then we might have account based systems instead of UT.
If we use Hyperledger or Corda, then we might have certificates instead of keys.
Similarly, other blockchain platforms have different types of core services which can be utilized with
the enterprise solutions.
So you need to make sure that you choose the blockchain platform which is suitable with your enterprise
needs.
So this is a generalized view for the blockchain module.
As we discussed, this blockchain module consists of data block.
This is the block of data and the schema for the data which is going to be hosted with your blockchain.
This could include your transactions, block header, block identity and Merkle tree.
Then you have chain structure chain structure is basically the structure of chain and how the chain
is going to be formed.
It could be that you are using two hashing algorithms.
It could be that you are using one single hashing algorithm.
So as per your enterprise needs, you will be forming the chain structure.
Then you have distributed hash table.
If this is required within your system, you might want to keep with the blockchain module.
If this is not required, you can opt it out.
Then you have Merkle Tree, which is part of major blockchain projects.
Most of the blockchain projects like Corda Bitcoin, Ethereum do have Merkle trees and use Merkle trees
for validation of transactions.
Then you have Axios.
Axios are unspent transaction outputs which are part of Bitcoin.
Many other blockchain platforms like Multichain also holds the principles of Axios.
Then you have hash function.
Hash function is used to protect the data.
They are one way function.
So once you take the hash of any data, you cannot go back.
Then you have digital signature.
Digital signature is used to verify the participants who are sending in the transactions.
So it could be that you might have a public blockchain coming in as a solution.
So digital signatures will be utilized there to verify that this message has been authenticated by the
correct participant.
Then you can also have cryptographic protocols as part of your blockchain module where you will define
which kind of algorithms and how these algorithms will work with the whole system.
So once you have defined your blockchain module, this blockchain module is going to be replicated to
all the different peers and nodes who are going to be part of your system.
So now let's go and learn the details about blockchain peers and nodes.