How alsotoes/momo works
Momo is a distributed, content-addressed object store. A client selects a daemon, hashes and optionally encrypts content, then sends it over the native protocol; the server stores the blob and coordinates configured replication. Users can also access objects through the S3-compatible gateway or the FUSE filesystem. The architecture includes pluggable blob backends, cluster placement and coordination, integrity/durability mechanisms, and optional distributed metadata and OPRF. Relationships for unsampled subsystems are shown only where the README documents them; some implementation details are therefore omitted.
Main entry points: server.go Server daemon · storage.go CAS store · client.go Native client · momo.go Momo runner
Components 23
Access surfaces
- Momo runner
src/momo.go - Native client
src/client/client.go
Cluster services
- Server daemon
src/server/server.go - Replication strategies
src/server/replication.go - P2P coordination
src/p2p/gossip.go - Distributed metadata
src/p2p/metadata_rpc.go - Cluster queries
src/server/query_handler.go - CRUSH placement
src/common/crush.go - Prometheus metrics
src/metrics/metrics.go
Storage and durability
- CAS store
src/storage/storage.go - Blob backends
src/storage/factory.go - Integrity verification
src/storage/integrity.go - Write durability
src/storage/durability.go - Rebuild
src/storage/rebuild.go
Protocols and security
- TCP / QUIC
src/transport/momo_tcp.go - S3 gateway
src/transport/s3_communicator.go - Client encryption / OPRF
src/crypto/envelope.go - OPRF service
src/server/oprf_service.go
Filesystem access
- FUSE adapter
src/momofs/fuse.go - POSIX namespace
src/momofs/momofs.go
Other components
- Operator / user
- S3 client
- POSIX user
Connections 27
- Operator / user → Momo runner: runs
- Momo runner → Native client: starts client
src/momo.go - Native client → TCP / QUIC: sends objects
src/client/client.go - TCP / QUIC → Server daemon: serves requests
- Server daemon → CAS store: stores objects
src/server/server.go - CAS store → Blob backends: stores blob bytes
src/storage/storage.go - Server daemon → Replication strategies: replicates writes
- Replication strategies → TCP / QUIC: forwards data
- Native client → CRUSH placement: chooses replicas
- Server daemon → P2P coordination: starts membership
src/server/server.go - Server daemon → Cluster queries: handles queries
src/server/query_handler.go - Cluster queries → CAS store: reads metadata
src/server/query_handler.go - P2P coordination → Distributed metadata: coordinates metadata
- Distributed metadata → CAS store: reads and writes
src/p2p/metadata_rpc.go - CAS store → Integrity verification: verifies content
- CAS store → Write durability: applies barrier
- Server daemon → Rebuild: rebuilds replicas
- S3 client → S3 gateway: requests objects
- S3 gateway → Server daemon: serves gateway
- Native client → Client encryption / OPRF: encrypts content
src/client/client.go - Server daemon → OPRF service: evaluates shares
src/server/oprf_service.go - Native client → Prometheus metrics: reports activity
- Operator / user → Momo runner: starts server
src/momo.go - POSIX user → FUSE adapter: uses filesystem
- Momo runner → FUSE adapter: starts FUSE
- FUSE adapter → POSIX namespace: adapts operations
src/momofs/fuse.go - POSIX namespace → CAS store: stores namespace data
src/momofs/momofs.go