How hiro-microdatacenters-bv/rhio works
Main components
• rhio core process: This is the central daemon that coordinates message routing and file syncing.
• rhio-operator: Acts as the Kubernetes operator managing CRDs and reconciliations for rhio services.
• NATS Server / JetStream: Acts as the messaging backbone for receiving and broadcasting messages.
• MinIO (or any S3-compatible store): Represents the external persistent objects storage for replicated files.
• HTTP API server (rhio-http-api): Supports health endpoints and status/control operations.
• Supporting libraries/crates:
• rhio-blobs: Handles the bao file encoding/decoding and file operations.
• rhio-config and rhio-core: Manage configuration and shared core types, such as message formats.
• Auxiliary components: Other tooling like s3-server for internal testing or simulation might be shown optionally.
Relationships and interactions
• The rhio process listens on a configured port and interacts with both internal cluster communications (via NATS) and external p2p messaging (via p2panda).
• It receives messages published to NATS (or JetStream), processes and routes them to other nodes.
• For file transfers, the process interacts with a local S3 bucket (MinIO) after encoding file content using bao and announces file availability over the network.
• The operator components (rhio-operator) would be shown managing configuration, CRDs, and deploying updates/fixtures within the Kubernetes cluster.
• A clear separation should be represented between external cluster messaging and internal file replication.
• Optionally, indicate how environment configurations, Helm charts, and ArgoCD overlays are used for deployment management.
Important architectural patterns and design principles
• Modular microservice design, achieved by splitting functionality into multiple Rust crates.
• Operator pattern for Kubernetes integration.
• P2P messaging and decentralized file distribution, emphasizing separation of concerns (message routing vs. file replication).
• Usage of standard configuration management practices (YAML-based configs, environment overlays, Helm charts).
Relevant technologies and frameworks
• Programming language: Rust (with multiple Cargo projects).
• Message queue: NATS Server with JetStream.
• Object storage: MinIO (or any S3-compatible system).
• Bao encoding for file handling.
• Kubernetes for deployment: Helm charts, ArgoCD applications, and CRDs via the rhio-operator.
• p2panda for decentralized messaging.