So now we have seen the different concepts which are going to be part of your identification manager.
This identification manager is connected to different modules.
As you can see in this diagram, we have internal systems application module, blockchain module and
integration module.
Internal systems is the legacy systems which are already operating with your enterprise applications.
It could also be that you are still developing your internal systems, but these are the core logics
for your enterprise solutions.
So now let's go and see what are the different concepts which are part of internal system and how a
common architecture for internal systems looks like.
Internal systems are the backbone for any enterprise and they hold the records and transactions which
are being processed with your enterprise solutions.
Most organizations keep the track of the transactions which are originating from their life cycle through
internal core ERP or core banking systems.
ERP are the Enterprise Resource Planning Solutions, and they offers the feasibility of integrating
the complete enterprise together.
Most of the internal systems operate on a three layered approach, but these internal systems could
also go up to 5 or 7 different layers.
Three layers are divided between database layer, business layer and application layer.
Database layer is the layer where most of the data is being hosted for the internal systems.
The business layer is the logic layer where most of the calculations are being performed for the internal
systems and the application layer are the applications where the data is being displayed after the processing
through the business layer.
Architecture for internal systems should always be designed by keeping security in mind because internal
systems are of utmost importance in any enterprise.
So this is a general view for the internal system.
Most of the internal systems are based upon the software architecture.
Here we are seeing a three tier architecture.
Three tier architecture have three different layers.
The first one is database layer, where most of the data related to the applications will be stored.
Anything related to users or asset will be part of the database.
The second layer is the business layer.
Business layer is taking the data from the database layer and then processing it.
This layer will hold the logic for the operations which are to be performed.
Let's say if you are creating a reporting based internal system.
So the data is directly present with database layer and the business layer takes up that data, perform
some calculations and generate some kind of information which can be required by the teams to analyze
the data.
So all those different logic calculations and arithmetic calculations will be done by the business layer.
Once those calculations are done, we have the third layer, which is known as a client.
We can also call it as a application layer.
Application layer is basically the output of data which has been processed.
So this is the display layer for your internal systems where the users will be able to see what has
happened inside the application.
This is a very generalized view for three tier architecture.
Your applications or your internal systems might also include five tier or a seven tier architecture
based upon your enterprise solutions.
Most of the organizations are already familiar with their internal systems because they have these systems
running from quite a long time.
But it could also be possibility that you are building the internal system from scratch within your
organization.
But whatever kind of strategy you are following for your enterprise blockchain solution, you need to
build up a integration module to integrate these internal systems with your blockchain modules.
So now let's go and see the details about integration module.