Backplane Deployment and Operation

i3-MARKET Artifacts

The artifacts involved in the R1 deployment have been classified into the following categories:

Third-party artifacts (black): these artifacts are dependencies that come from open-source software. In i3-MARKET R1 they have been identified as the following:
- Hyperledger Besu (blockchain network)
- CockroachDB (distributed storage)
- RocksDB (ledger)
- Loopback4 (i3Market backplane API)
i3-MARKET artifacts (green): SW pieces to be developed in the context of i3-MARKET, mainly provided in Wp3 and Wp4.
i3-MARKET SDK artifacts (orange): SDK software to be developed in the context of i3-MARKET and deployed on the external actor’s side.

i3-MARKET SW and Third-party SW layers assignments

SW COMPONENT	BUILDING BLOCK	TYPE	TECHNOLOGY
Blockchain Framework	—	Third-party SW	Hyperledger Besu
Distributed Storage	Data Storage	Third-party SW	CocroachDB
Decentralized Storage	Data Storage	Third-party SW	RocksDB.
Security Server	Trust, Security and Privacy	Third-party SW	Keycloack
User-centric Authentication	Trust, Security and Privacy	i3Market SW
Service-centric Authentication	Trust, Security and Privacy	i3Market SW
Cloud Wallet	Trust, Security and Privacy	i3Market SW
SW Wallet	Trust, Security and Privacy	i3Market SW
HW Wallet	Trust, Security and Privacy	i3Market SW
Smart Contract Manager	Trust, Security and Privacy	i3Market SW
Conflict Resolution	Trust, Security and Privacy	i3Market SW
Explicit user-concern	Trust, Security and Privacy	i3Market SW
Auditable Accounting	Trust, Security and Privacy	i3Market SW
Standard payments	Trust, Security and Privacy	i3Market SW
Micro-payments	Trust, Security and Privacy	i3Market SW
Tokenization	Trust, Security and Privacy	i3Market SW
Data Access SDK	—-	i3Market SW
Data Access API	Data Access	i3Market SW
Semantic Storage	Semantics	i3Market SW + Third P. SW
Metadata Management	Semantics	i3Market SW
Semantic Orchestration (Offering and Discovery)	Semantics	i3Market SW
Backplane API	Backplane	i3Market SW	LOOPBACK4
i3Market SDK	—-	i3Market SW

i3-MARKET Deployment Diagrams

Based on the overall architecture and the building block specifications i3-MARKET has created an operation specification for the Backplane that specifies the details and how all the building blocks comprising the Backplane will be integrated, deployed and monitored. Since at least 3 instances of the Backplane will be operated in the cloud, the first step will be to setup the cloud environments for that deployments. Then the operation specification is used to actually operate the i3-MARKET Backplane instances.

The first version of the deployment specification will be released in M16 (D4.4a). This version will be used for the first release of the operational Backplane in M18 (D4.9a). A second version of the specification, that will include the lessons learned from the first release and the further development of the building block tasks, will be released in M20 (D4.4b) and will be used for the final operational Backplane in M22 (D4.9b).

A final version of the specification, that will include the final updated from the industry pilots and the further development of the building block tasks according to the pilots execution, will be released in M31 (D4.4c) and will be used for the final operational Backplane in M33 (D4.9c).

The diagrams that are used to visualise and design the deployment can be viewed here.

Disclaimer

The i3-Market project has received funding from the European Union’s Horizon 2020 Research and Innovation Programme under grant agreement no. 871754.

Contact