NEW
A system design where control, computation, and data are distributed across nodes without a single central authority.
DESCRIPTION
Decentralized architecture distributes decision-making and resources across multiple nodes or domains. It reduces single points of failure and can improve scalability and resilience. Peer-to-peer networks, blockchains, and federated systems exemplify decentralization. Governance, consistency, and coordination become key challenges. Communication patterns rely on messaging, consensus, or event-driven mechanisms. Data ownership and locality drive privacy and compliance benefits. Decentralization complements microservices and edge computing. Trade-offs include operational complexity and eventual consistency. It requires robust observability, security, and coordination protocols.
ALTERNATIVE DEFINITIONS
Wikipedia
Decentralized computing is the allocation of resources, both hardware and software, to each individual workstation or office location.
Focuses on resource allocation away from central systems.
Wikipedia
Distributed computing is a field of computer science that studies distributed systems.
Situates decentralization within distributed systems theory and practice.
RELATED TERMS
Distributed Systems Peer-to-Peer Microservices Blockchain Edge Computing Event-Driven Architecture CAP Theorem Consensus Federated Learning
COMPETING TERMS
KNOWLEDGE AREAS
Data Architecture Infrastructure Cloud Data Integration & Interoperability
TARGET AUDIENCE
Data Architect Cloud Architect Enterprise Architect Software Developer
EXTERNAL SOURCES
- Wikipedia - Decentralized computing
- NIST - Blockchain overview and decentralization concepts
- W3C - Decentralized identifiers architecture
- CNCF - Cloud native patterns for distributed systems
TOP QUESTIONS
Why choose a Decentralized Architecture?
To reduce single points of failure, improve resilience, align with data sovereignty, and scale across domains or edges.
Category: Relevancy
What are the main risks of Decentralized Architecture?
Increased operational complexity, coordination overhead, and challenges with consistency, security, and governance across nodes.
Category: Risks
How does Decentralized Architecture relate to microservices?
Microservices decentralize application responsibilities; the architecture extends this to ownership, data, and infrastructure across domains.
Category: Example
Is Decentralized Architecture the same as distributed systems?
They overlap. Decentralization emphasizes autonomy and no central authority, while distributed systems focus on components across networked nodes.
Category: Misunderstanding
How is data consistency handled in decentralized systems?
Through consensus protocols, event sourcing, and eventual consistency patterns balanced by business requirements.
Category: Requirements
What’s a common mistake when adopting Decentralized Architecture?
Fragmenting governance and security controls without establishing federated standards and shared services.
Category: Mistakes
How does Decentralized Architecture support data sovereignty?
Data remains within jurisdictions or domains, with policies enforced locally and federation enabling controlled sharing.
Category: Example
What patterns enable coordination without central control?
Publish/subscribe, saga pattern, CRDTs, and consensus algorithms like Raft or Byzantine fault-tolerant protocols.
Category: Example
When is a centralized approach preferable?
For small teams, strict consistency needs, or simple domains where centralized governance reduces complexity.
Category: Opinion