What is Decentralization in Blockchain?
What is decentralization?
In blockchain, decentralization refers to the transfer of control and decision-making from a centralized entity (individual, organization, or group thereof) to a distributed network. Decentralized networks strive to reduce the level of trust that participants must place in one another, and deter their ability to exert authority or control over one another in ways that degrade the functionality of the network.
Why decentralization matters
Decentralization is not a new concept. When building a technology solution, three primary network architectures are typically considered: centralized, distributed, and decentralized. While blockchain technologies often make use of decentralized networks, a blockchain application itself cannot be categorized simply as being decentralized or not. Rather, decentralization is a sliding scale and should be applied to all aspects of a blockchain application. By decentralizing the management of and access to resources in an application, greater and fairer service can be achieved. Decentralization typically has some tradeoffs such as lower transaction throughput, but ideally, the tradeoffs are worth the improved stability and service levels they produce.
Benefits of decentralization
How decentralization compares
Decentralization should be applied where it makes sense. Just because it’s a blockchain application doesn’t mean it needs to be 100% decentralized. The goal of any blockchain solution is to deliver what the users of that solution need, and this may or may not include certain levels of decentralization. To better understand decentralized networks, the table below breaks out how decentralized networks compare to the more common centralized and distributed networks.
|
Centralized |
Distributed |
Decentralized |
Network/hardware resources |
Maintained & controlled by single entity in a centralized location |
Spread across multiple data centers & geographies; owned by network provider |
Resources are owned & shared by network members; difficult to maintain since no one owns it |
Solution components |
Maintained & controlled by central entity |
Maintained & controlled by solution provider |
Each member has exact same copy of distributed ledger |
Data |
Maintained & controlled by central entity |
Typically owned & managed by customer |
Only added through group consensus |
Control |
Controlled by central entity |
Typically, a shared responsibility between network provider, solution provider & customer |
No one owns the data & everyone owns the data |
Single Point of Failure |
Yes |
No |
No |
Fault tolerance |
Low |
High |
Extremely high |
Security |
Maintained & controlled by central entity |
Typically, a shared responsibility between network provider, solution provider & customer |
Increases as # of network members increase |
Performance |
Maintained & controlled by central entity |
Increases as network/hardware resources scale up and out |
Decreases as # of network members increase |
Example |
ERP system |
Cloud computing |
Blockchain |
Each network architecture has its benefits and tradeoffs. For example, decentralized blockchain systems, unlike distributed systems, typically prioritize security over performance. So, when a blockchain network scales up or out, the network becomes more secure, but performance slows down because each member node must validate all data being added to the ledger. Adding members to a decentralized network can make it safer, but not necessarily faster.