Conceptual View

This section describes the object model of the design.

Layers

According to Dan Boneh Blockchain applications may be divided into four layers:

3	User Interface
2	Applications
1.5	Compute Layer
1	Consensus Layer

We will use this classifications to group Iroha components and 3rd party components that can be integrated with Iroha components.

Components

Layer	Components	Description
User Interface	Iroha Clients + 3rd Party Clients Web/Mobile/CLI	User Facing Services
Applications	Iroha Modules + Custom Iroha Special Instructions	Run on blockchain computer
Compute Layer	Iroha + Iroha Modules + Iroha Special Instructions	Application logic is encoded in a program that runs on blockchain • Rules are enforced by a public program (public source code) ➔ transparency: no single trusted 3rd party • The APP program is executed by parties who create new blocks ➔ public verifiability: anyone can verify state transitions
Consensus Layer	Iroha Sumeragi	A public data structure (ledger) that provides: Persistence: once added, data can never be removed Consensus: all honest participants have the same data Liveness: honest participants can add new transactions Open(?): anyone can be a participant (no authentication)

Plant UML

@startuml
cloud "User Interface" {
  [Mobile Application]
  [Web Application]
  [Command Line Interface]
}


database "Compute Layer" {
  [Iroha]

  node "Applications" {
    [Iroha Substrate]
  }

  folder "Consensus" {
    [Sumeragi]
  }
}


[Mobile Application] --> [Iroha]
[Web Application] --> [Iroha]
[Command Line Interface] --> [Iroha]
@enduml

Application Programming Interface

Functionality	Provider	Description
Submission of Iroha Special Instructions	Clients	Clients receive declaration of desired actions from users in form of Iroha Special Instructions. They build a Transaction from them, use User's cryptographics keys to Sign it (optionally?) and send them to Iroha.
Sending of Iroha Queries	Clients	Clients receive declaration of desired search results from users in form of Iroha Queries. They build a Request from them, use User's cryptographics keys to Sign it (optionally) and send them to Iroha.
Execution of Iroha Special Instructions	Iroha	Iroha receives Transactions from Clients and process them in cooperation with Applications and Consensus. More on that in Process View Section.
Execution of Iroha Queris	Iroha	Iroha receives Queries from Clients and execute them. More on that in Process View Section.

Process View

This section describes the activities of the system, captures the concurrency and synchronization aspects of the design.

Physical View

This section describes the mapping of software onto hardware and reflects its distributed aspect.

Development View

This section describes the static organization or structure of the software in its development of environment.

Scenarios

{"include":"authors, comments","showCount":"true","contextEntityId":31204854}

Version	Published	Changed By
CURRENT (v. 9)	Aug 24, 2020 12:55	Vadim Reutskiy
v. 25	Aug 24, 2020 12:53	Vadim Reutskiy
v. 24	Aug 24, 2020 12:53	Vadim Reutskiy
v. 23	Aug 24, 2020 12:52	Vadim Reutskiy
v. 22	Aug 24, 2020 12:51	Vadim Reutskiy
v. 21	Aug 24, 2020 12:44	Vadim Reutskiy
v. 20	Aug 24, 2020 12:37	Nikita Puzankov
v. 19	Aug 24, 2020 05:27	Vadim Reutskiy
v. 18	Jul 13, 2020 10:19	Nikita Puzankov
v. 17	Jul 09, 2020 09:11	Nikita Puzankov

Go to Page History

Page tree

Architecture