How kartikx/distributed-file-system works
Project type and purpose
• From the file tree and code names (main.go, server.go, client.go, introducer.go, ring.go, piggyback.go, membershipInfo.go, messages.go, caching.go, file.go), this is a Go-based distributed systems project implementing a membership/gossip protocol and file‐service API across a cluster. The “introducer” suggests a bootstrap node, “ring” indicates a logical overlay, and “piggyback” implies gossip piggybacking.
File structure
• Top-level Go sources:
• main.go – application entry point
• server.go / client.go – RPC or REST stubs for service and client operations
• introducer.go – cluster join coordinator
• ring.go – ring overlay management
• piggyback.go / messages.go / membershipInfo.go – gossip protocol and membership state
• caching.go / file.go – file‐service logic and caching layer
• utils.go / constants.go / logger.go – shared utilities, configuration, and logging
• demo/ and bash_scripts/ – setup and demo scripts (not part of runtime).
• go.mod/go.sum – module and dependencies.
Key README insights
• The README is the default GitLab template and does not describe architecture. We infer architecture purely from code.