Chromia architecture

The integral relational database makes Chromia a full-stack decentralized development platform. This means that it includes all the layers necessary to build complete applications.

Before going into each component in detail, let's see the high-level architecture of Chromia.

Providers play a key role in the Chromia ecosystem. Chromia acquires node capacity from the Providers. Nodes run by providers produce blocks, thus enabling dapps to run. In Chromia, nodes are arranged in clusters that run blockchains. For more information, see nodes.

Clients connect to nodes to post transactions or query data. Chromia uses a modified version of the PBFT (Practical Byzantine Fault Tolerance) protocol called eBFT for consensus, where validator nodes validate transactions and blocks.

If you want to create a dapp, you can write the backend in Rell and deploy it to the Chromia platform. Chromia also has client libraries for building transactions on the frontend. The client-side then sends the transactions to the Rell backend. You can read about this structure in the Rell Introduction section.