add links - formatting
This commit is contained in:
@@ -510,20 +510,34 @@ Bare provides only the essential primitives: process management, file system acc
|
||||
|
||||
### The Modules That Make It Work
|
||||
|
||||
The native host leverages several interconnected modules from the Hyper ecosystem to provide complete P2P functionality.
|
||||
The native host leverages several interconnected modules from the **[Hyper ecosystem](https://holepunch.to/)** (maintained by **[Holepunch](https://github.com/holepunchto)**) to provide complete P2P functionality.
|
||||
|
||||
Hyperswarm is the networking layer that handles peer discovery and connection establishment. It uses a distributed hash table where peers announce their interest in specific topics. When your application calls join on a topic, Hyperswarm announces to the DHT that you're interested in that topic. Other peers doing the same will be discovered, and Hyperswarm attempts to establish direct connections. This discovery mechanism is entirely decentralized with no central server required.
|
||||
#### **[Hyperswarm](https://github.com/holepunchto/hyperswarm)**
|
||||
|
||||
Hyperswarm is the networking layer that handles peer discovery and connection establishment. It uses a distributed hash table where peers announce their interest in specific topics. When your application calls `join` on a topic, Hyperswarm announces to the DHT that you're interested in that topic. Other peers doing the same will be discovered, and Hyperswarm attempts to establish direct connections. This discovery mechanism is entirely decentralized with no central server required.
|
||||
|
||||
#### **[Corestore](https://github.com/holepunchto/corestore)**
|
||||
|
||||
Corestore provides the storage foundation that the other data modules build upon. It's essentially a system for managing multiple Hypercore instances, each with their own cryptographic key. When you need to store data in Hyperbee or Hyperdrive, Corestore creates and manages the underlying Hypercore that those systems use. It handles the key management so you don't have to think about it.
|
||||
|
||||
#### **[Hypercore](https://github.com/holepunchto/hypercore)**
|
||||
|
||||
Hypercore is an append-only log, similar to a blockchain but without the proof-of-work consensus. Data is added in sequence, cryptographically linked to previous entries, and can be verified by anyone with the core's public key. It's the fundamental data structure that Hyperbee and Autobase build upon. For P2P applications, Hypercore provides tamper-evident logging that can be replicated between peers.
|
||||
|
||||
#### **[Hyperbee](https://github.com/holepunchto/hyperbee)**
|
||||
|
||||
Hyperbee builds on Hypercore to provide a B-tree key-value store. Think of it like Redis but distributed and peer-to-peer. You put key-value pairs in, you get them out, and the data replicates automatically between connected peers. The B-tree structure makes lookups efficient even with millions of keys.
|
||||
|
||||
#### **[Hyperdrive](https://github.com/holepunchto/hyperdrive)**
|
||||
|
||||
Hyperdrive is a P2P file system built on Hyperbee. You can create files and directories, read and write content, and everything syncs automatically between peers who are interested in the same drive. It's like having a shared filesystem that requires no server, where anyone with the drive key can read and write.
|
||||
|
||||
#### **[Autobase](https://github.com/holepunchto/autobase)**
|
||||
|
||||
Autobase is a multi-writer version of Hypercore. Regular Hypercore has a single writer, but Autobase allows multiple peers to append to the same log while maintaining a consistent ordering through a linearization mechanism. This is crucial for collaborative applications where multiple users might make changes simultaneously.
|
||||
|
||||
#### **[Hyperdb](https://github.com/holepunchto/hyperdb)**
|
||||
|
||||
Hyperdb adds schema and query capabilities on top of these primitives. Rather than just storing raw key-value pairs, you define collections with specific fields. It handles the complexity of replication, conflict resolution, and querying so you can work with a familiar database-like interface while the P2P magic happens underneath.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user