2 |
3 |
4 |
5 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
22 | Chainode is a private blockchain designed to be fast, lightweight, and highly scalable. The network allows to exchange data (transactions) between trusted participants. These transactions are stored as blocks in a distributed ledger. 23 |
24 | 25 |Highly scalable
29 |30 | Each peer can be deployed, executed, and scaled up and down asynchronously and independently from the others peers. 31 | Peers can be runned as containers on different clusters handled by different container orchestrators (like Kubernetes, Mesos, etc). 32 |
33 |Load balancing
37 |38 | Designed to support high data volumes, the blocks and the ledger are load balanced: the blocks are distributed between different peers that acts as a single one, sharing the same Kafka group id. 39 |
40 |Resilient
48 |49 | Each peer is resistant to failures. If a peer service (or the node where it is running) falls, it can be immediately restarted on another node without (thanks to Kafka retention features) losing data and starting from where he had stopped. 50 |
51 |Fast
55 |56 | Every block is propagated to the network and added to the ledger as soon as it was generated (if it was considered valid by the peers), so without any delay or emission at every defined time interval. 57 |
58 |Lightweight
66 |67 | A chainode instance (a simple peer) is very lightweight: can be runned on cheap machines (like a Raspberry Pi, so as many docker containers on a single machine). 68 |
69 |Message driven
73 |74 | The network communication is Kafka based. The peers communicate with each other by exchanging messages asynchronously. Communication can be public or private. 75 |
76 |REST APIs
84 |85 | Every peer exposes web APIs to be handled more easily by other applications. 86 |
87 |Web Console
91 |92 | Every peer exposes a Web Console UI for status monitoring, use, and general testing too. 93 |
94 |Open Source
102 |103 | Chainode is an Open Source project, written in pure Javascript for Node.js, and it is based on Kafka as communication system and block order. 104 | The documentation is Creative Commons Licensed. 105 |
106 |Status | 10 |{{STORE.system.status}} | 11 |
Blockchain | 14 |{{STORE.system.peer.blockchain}} | 15 |
Id | 18 |{{STORE.system.peer.id}} | 19 |
Role | 22 |{{STORE.system.peer.role}} | 23 |
Organization | 26 |{{STORE.system.peer.organization}} | 27 |
Uptime | 30 |{{STORE.system.peer.role | timeDuration}} | 31 |
Used memory | 34 |{{STORE.system.system.memoryUsage.heapTotal | formatBytes}} | 35 |
Free memory | 38 |{{STORE.system.system.freemem | formatBytes}} / {{STORE.system.system.mem | formatBytes}} | 39 |
6 | List of transactions of the ledger. 7 |
8 | 9 |10 | There are no blocks... 11 |
12 | 13 |id | 19 |event_id | 20 |organization | 21 |generated_time | 22 |data | 23 |
---|---|---|---|---|
{{block.id | readMore(10)}} | 28 |{{block.event_id | readMore(10)}} | 29 |{{block.organization | readMore(10)}} | 30 |{{block.generated_time | dateMedium}} | 31 |{{block.data | readMore(20)}} | 32 | 35 |
6 | Compose a new transaction to candidate as block into the ledger. 7 |
8 | 9 | 17 | 18 |