Architecture
In centralized database services, data is created from an application and stored on one or two servers that can be located in a specific place. With Bluzelle, the data is stored on a network of 13 or more nodes. Each such network is called a database zone, and all zones are synced together. No node is a leader, ensuring that if a node is offline, the data is still available as all the other nodes have a copy. Additionally, because all the nodes are synced with a consensus engine, no changes can be made to the database unless ⅔ of the nodes agree. This ensures that the data is censorship resistant and tamper-proof. Finally, as an application requires more storage, more database zones can be added, ensuring scalability without the developer needing to do extra work and provisioning.
Bluzelle consists of many components that work together.
Database Engine - A NoSQL key-value store database. It is built using the Cosmos SDK.
BFT Consensus Engine - Powered by Tendermint, this component ensures all the node remain in sync.
Nodes - the core foundation of Bluzelle is operated by nodes which are provided by the public community. They provide the storage space and execute changes through consensus in return for a fee.
Bluzelle token (BLZ) - an Ethereum based ERC-20 token is easily obtained outside the Bluzelle network. It is on top exchanges like Binance, Huobi, Uniswap and others. There also exists the BLZ Mainnet token that is used for Bluzelle services within the ecosystem. BLZ ERC-20 and BLZ Mainnet are interchangeable through via Bluzelle's main dashboard.
Client Library - the interface to talk to Bluzelle. Currently in Javascript. Will support others.
Client Proxy - allows the client to trust the response given by a decentralized network
Bluzelle Studio - an interactive web app that allows developers to work with the database
Zone - a blockchain comprised of a collection of nodes. There are three types of zones.
Database zones - the building blocks to provide capacity for the database network. As more capacity is required, more database zones are added. This is for scalability.
Peg zone - a special blockchain of nodes that provides a decentralized means to bridge the database zones with other networks like Ethereum.
Hub zone - allows the database zones and peg zone to communicate with one another
Last updated