orbitdb/orbitdb
Orbitdb
OrbitDB is a decentralized data storage system that enables the creation of serverless databases residing across a network of peers. It functions as a peer-to-peer database that integrates with a content-addressed storage layer to distribute and replicate data without a central server.
The system utilizes conflict-free replicated data types to ensure eventual consistency and state convergence across distributed nodes. It maintains an immutable record of updates using a directed acyclic graph to preserve causal ordering and cryptographic integrity. Access is managed through a decentralized identity system that uses public-key cryptography to verify write permissions and authenticate users.
The project provides capabilities for distributed data modeling, including document stores and append-only logs. It supports browser-based networking through relay servers and bridging mechanisms that allow web environments to connect to peer networks. Security is handled via pluggable encryption modules and customizable access validation logic.
The implementation allows for extensibility through custom identity providers, tailored storage backends, and user-defined data models.
Features
- Decentralized Storage - Provides a serverless database system that resides across a network of peers using decentralized storage.
- CRDT Databases - Provides a decentralized database using conflict-free replicated data types to ensure eventual consistency across all nodes.
- Concurrent Update Resolution - Uses a deterministic sort function to order simultaneous updates and determine the final database state.
- Content-Addressable Storage - Implements a storage layer where data is identified by cryptographic hashes, enabling decentralized distribution and retrieval.
- Distributed Data Synchronization Systems - Maintains various data models, including immutable logs and document stores, across a network of peers.
- Distributed Databases - Initializes serverless data stores to distribute data across a decentralized network.
- IPFS-Based Databases - Leverages IPFS for content-addressed storage and data replication across a decentralized network.
- Append-Only Log Storage - Maintains an immutable, distributed record of updates using a Merkle-DAG for causal ordering.
- Peer-to-Peer Synchronization Engines - Uses conflict-free replicated data types to keep data consistent across multiple devices and networks.
- Conflict-Free Replicated Data Types - Uses conflict-free replicated data types to merge concurrent writes and ensure all nodes converge.
- Distributed Database Synchronization - Synchronizes database state between distributed nodes by connecting peers via unique addresses.
- Peer-to-Peer Networking - Enables direct node-to-node communication using multiaddresses and dial functions for data retrieval.
- PubSub Message Propagation - Propagates database updates across a decentralized network using a publish-subscribe mechanism to synchronize state.
- Identity and Access Management - Uses cryptographically signed identities to control write access and authenticate users in a decentralized environment.
- Decentralized Write Permissions - Provides a security layer using public-key cryptography to manage write permissions and identity verification.
- Cryptographic Identity Verification - Verifies write access and data authenticity by matching signed updates against a set of trusted public keys.
- Write Permission Controls - Enforces write permissions for specific peers to ensure data integrity across the decentralized network.
- Merkle-DAG - Maintains an immutable distributed record of updates using a directed acyclic graph to preserve causal ordering.
- Immutable Logs - Maintains an immutable distributed record of updates using Merkle-DAGs to ensure causal ordering.
- Decentralized Identity Engines - Fetches identity data as linked data objects from a decentralized network using content hashes.
- Custom Data Models - Allows implementation of new data structures that inherit cryptographic verification and replication properties.
- Cryptographic Commit Logs - Uses a Merkle-DAG as a cryptographic commit log to maintain a verified causal order of updates.
- Storage Backend Adapters - Provides an adapter pattern for swapping default storage mechanisms with custom persistent backends.
- Custom Identity Providers - Supports alternative authentication systems through custom logic for identity generation and signing.
- Browser-Based Connectivity - Enables web browsers to connect to peer networks using WebRTC and relay servers.
- Distributed Document Stores - Implements a decentralized document store allowing peers to synchronize and query shared data models.
- TURN Relays - Uses relay servers and WebRTC to route traffic and connect browsers to the peer network.
- WebSocket to Stream Bridges - Routes traffic between browser environments and server daemons to bypass raw network socket restrictions.
- Data Encryption - Secures payload data using customizable encryption modules that can be swapped based on security requirements.
- Payload Encryptions - Provides pluggable encryption modules to secure stored payload data and replication logs against unauthorized access.
- Identity-Based Access Restrictions - Implements identity-based restrictions to control which users or peers can modify identities via immutable lists or grant-and-revoke systems.
- Pluggable Encryption Modules - Provides support for custom encrypt and decrypt functions to apply specialized cryptographic logic to stored data.
- Access Validators - Supports custom validation functions to determine if specific data entries can be appended to the store.
- Browser-to-Server Channels - Bridges browser nodes to server daemons using WebSockets to bypass raw TCP/QUIC restrictions.
- Storage Engine Interfaces - Decouples database logic from physical storage through a standard interface for record retrieval and insertion.
