How akashcx/chord-p2p-file-sharing-system works
Project Components
• Bootstrap Node: The central entry point initiating the chord network. It’s clearly the “bootstrap” container that the README refers to.
• Peer Nodes: Multiple containers (scaled via Docker Compose) that form the P2P network and participate in file transfer operations.
• Node Internal Logic: In the “node” directory, you have files such as assembler.go, chunker.go, message.go, and node.go indicating internal functionalities—assemble data, break it into chunks, handle messaging, and node behavior respectively.
• Utilities and Supporting Logic: The “utils” folder houses helper functions (utils.go) that likely support operations across nodes.
• Data Layer: The “data” folder contains files (like file.txt and a video file) which are likely used in demonstrating file transfer capabilities.
• Infrastructure & Orchestration: The Dockerfile, docker-compose.yml, and the overall Docker-based orchestration underline how the containers are built and interact.
Architecturally Significant Patterns
• Container-based Deployment: Highlight Docker’s role in orchestrating the bootstrap and peer nodes.
• Modularity in Node Functionality: The separation between assembling, chunking, and messaging within the node indicates a modular structure internally.
• One for the "Bootstrap Node"
• Message handling (from message.go)
• Data chunking (from chunker.go)
• Assembling files (from assembler.go)
• Another for core application components (bootstrap and peers)