<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>s3-orchestrator diagrams :: s3-orchestrator</title><link>https://s3-orchestrator.munchbox.cc/diagrams/index.html</link><description>Interactive architecture and flow diagrams for the S3 Orchestrator internals. System Architecture End-to-end architecture showing the request path, storage layer, background services, and observability.
Admission Control Flow Detailed request lifecycle through admission control, authentication, routing, and circuit breakers.
Write Path PutObject flow through backend selection, encryption, failover, and metadata recording.
Read Path GetObject flow through location lookup, failover, broadcast reads, decryption, and streaming.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://s3-orchestrator.munchbox.cc/diagrams/index.xml" rel="self" type="application/rss+xml"/><item><title>System Architecture</title><link>https://s3-orchestrator.munchbox.cc/diagrams/architecture/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/architecture/index.html</guid><description>High-level architecture of the S3 Orchestrator showing the request path, storage layer, background services, and observability. Hover over any component for implementation details.</description></item><item><title>Admission Control Flow</title><link>https://s3-orchestrator.munchbox.cc/diagrams/admission-control/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/admission-control/index.html</guid><description>This interactive diagram shows the complete request lifecycle through the S3 Orchestrator’s admission control pipeline. Hover over any node to highlight its upstream/downstream path and see implementation details.</description></item><item><title>Write Path</title><link>https://s3-orchestrator.munchbox.cc/diagrams/write-path/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/write-path/index.html</guid><description>Detailed flow of a PutObject request through backend selection, encryption, failover, and metadata recording. Hover over any component for implementation details.</description></item><item><title>Read Path</title><link>https://s3-orchestrator.munchbox.cc/diagrams/read-path/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/read-path/index.html</guid><description>Detailed flow of a GetObject request through location lookup, failover, broadcast reads, decryption, and streaming. Hover over any component for implementation details.</description></item><item><title>Circuit Breaker</title><link>https://s3-orchestrator.munchbox.cc/diagrams/circuit-breaker/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/circuit-breaker/index.html</guid><description>Three-state circuit breaker state machine shared by the database wrapper (CircuitBreakerStore) and per-backend wrapper (CircuitBreakerBackend). Hover over any component for implementation details.</description></item><item><title>Encryption Flow</title><link>https://s3-orchestrator.munchbox.cc/diagrams/encryption/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/encryption/index.html</guid><description>Envelope encryption and decryption paths for S3 objects using chunked AES-256-GCM with pluggable key providers. Hover over any component in the diagram for implementation details.
How it works When encryption is enabled, every object stored through the S3 Orchestrator is encrypted before it leaves the server. The system uses envelope encryption — a two-layer key scheme where each object gets its own throwaway key, and that key is itself encrypted by a master key. Encryption is optional — see the configuration reference for how to enable it.</description></item><item><title>Background Services</title><link>https://s3-orchestrator.munchbox.cc/diagrams/background-services/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/background-services/index.html</guid><description>Coordination of periodic background workers that maintain storage health, enforce replication, and persist counters. Hover over any component for implementation details.</description></item><item><title>Database Schema</title><link>https://s3-orchestrator.munchbox.cc/diagrams/database-schema/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://s3-orchestrator.munchbox.cc/diagrams/database-schema/index.html</guid><description>Entity-relationship diagram of the PostgreSQL metadata store. Hover over any table for column details and usage context.</description></item></channel></rss>