MinIO

# MISSION: Scaffold "MinIO" Production Architecture
You are an expert Senior Staff Software Architect and Full-Stack Engineer. Your mission is to scaffold and implement a production-grade, highly reliable, and modular codebase following the proven architecture of **MinIO**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: MinIO
- **What It Does**: MinIO is a Go implementation of the S3 API: an erasure-coded object store (klauspost/reedsolomon) with optional etcd-backed distributed IAM, LDAP and OpenID Connect identity integration, and tiering to Azure Blob Storage or Google Cloud Storage.
- **Domain & Category**: High-Performance S3 Object Storage
- **Production Scale**: 20+ people
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Implementing erasure coding, IAM, and multi-protocol event notifications directly in the Go server, instead of delegating to RAID or an external message broker, keeps a deployment to a single binary while still integrating with existing enterprise identity and messaging systems through native client libraries.
- **Live Website Reference**: https://min.io
- **Source Repository**: https://github.com/minio/minio
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Go, S3, Docker, Prometheus, Kubernetes
- **Primary Language(s)**: Go
- **License of the reference repo**: AGPL-3.0
- **Backend & APIs**: Go — Implements the entire server, including the S3 API handlers under cmd/.; Erasure coding (Reed-Solomon) — Encodes objects across drives for redundancy and self-healing, implemented in cmd/erasure-*.go.; etcd — Optional distributed backend for IAM and configuration state alongside the local object store.; LDAP — External identity provider integration for admin-managed users and groups.; OpenID Connect — External identity provider integration via OIDC, alongside LDAP, for admin authentication.
- **Data & persistence**: S3 — MinIO implements Amazon's S3 API directly; this is the primary object storage protocol it serves.; Azure Blob Storage — Tiering target for moving colder objects out of local erasure sets.; Google Cloud Storage — Tiering target alongside Azure Blob Storage for cold object data.; Event notification targets — Publishes bucket events to Kafka, NATS, NSQ, RabbitMQ, MQTT, Redis, MySQL, PostgreSQL, and Elasticsearch.
- **Infrastructure & deploy**: Docker — Release image copies prebuilt platform binaries into a minimal container.; Kubernetes — Ships a Helm chart, linted in CI, for cluster deployment.; Prometheus — Exposes cluster, drive, and API metrics through the built-in metrics endpoints.
- **Tooling, testing & ops**: GitHub Actions — Runs Go linting, resiliency and healing test suites, and dependency vulnerability checks.; Mint — MinIO's own S3-API compliance test suite, run in CI against built server binaries.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/minio/minio @ 7aac2a2)
1. **The project is now archived with an explicit deprecation notice**: GitHub marks the repository archived, and README.md opens with a callout stating this repository is no longer maintained, pointing users to AIStor Free and AIStor Enterprise as replacements, so the audited commit reflects the final state of the community-maintained server rather than an actively developed one.
2. **IAM and config state can be distributed via etcd, not only local disk**: go.mod depends directly on go.etcd.io/etcd/api/v3 and client/v3, and cmd/iam-etcd-store.go implements an etcd-backed IAM store alongside cmd/iam-object-store.go, so multi-node deployments can centralize identity and policy state in etcd instead of each node holding it independently.
3. **Enterprise identity integrates through LDAP and OpenID Connect**: go.mod depends on go-ldap/ldap and coreos/go-oidc, and cmd/admin-handlers-idp-ldap.go and cmd/admin-handlers-idp-openid.go implement dedicated admin API handlers for each, so external identity providers plug in through standard protocols rather than a MinIO-specific directory service.
4. **Data redundancy is application-level erasure coding, not RAID**: go.mod depends on klauspost/reedsolomon, and cmd/erasure-encode.go, cmd/erasure-decode.go, and cmd/erasure-healing.go implement Reed-Solomon encoding and self-healing across drives in Go, so redundancy is handled by the MinIO process itself rather than a hardware or filesystem RAID layer.
5. **Tiering targets other object stores rather than a proprietary cold format**: go.mod depends on cloud.google.com/go/storage and github.com/Azure/azure-sdk-for-go/sdk/storage/azblob, so colder data can move to Google Cloud Storage or Azure Blob Storage using their native SDKs instead of a MinIO-specific archive format.
6. **Bucket notifications fan out to general-purpose messaging systems**: go.mod depends directly on IBM/sarama (Kafka), nats-io/nats-server and nats.go, nsqio/go-nsq, rabbitmq/amqp091-go, and eclipse/paho.mqtt.golang, so bucket event notifications are implemented as native clients for each of these systems rather than one generic webhook mechanism.
---
## 4. NON-NEGOTIABLE ARCHITECTURAL GUARDRAILS
1. **Monorepo & Modular Separation**:
   - Structure as a Turborepo monorepo with strict package boundaries:
     - `apps/web`: Application UI, routing, layouts, and server endpoints.
     - `packages/ui`: Shared design tokens, CSS variables, and Radix UI primitive components.
     - `packages/db`: Database schemas, client singleton, declarative migrations, and seed scripts.
     - `packages/config`: Shared TypeScript, ESLint, and build configurations.
2. **Strict Type Safety & Zero `any` Policy**:
   - Enable `strict: true`, `noImplicitAny: true`, and `strictNullChecks: true`.
   - Validate ALL external inputs, API request bodies, and query parameters with **Zod** schemas before execution.
3. **Frontend & Rendering Guidelines**:
   - Isolate interactive UI state to leaf components. Keep core pages lightweight and performant.
4. **Design System & Aesthetics**:
   - Keep every color, radius, shadow and font in a single token file (CSS variables) and consume tokens everywhere; never hardcode hex values in components.
   - Prefer crisp 1px borders and one subtle shadow scale over blurry default shadows. Pair one sans-serif for body/headings with one monospace for tags, badges, metrics, and code.
5. **Data Layer & Reliability**:
   - Write declarative schema definitions with foreign keys, composite indexes on queried filters, and automated timestamp triggers.
   - Use connection pooling and prepared statements for serverless database execution.
---
## 5. STEP-BY-STEP SCAFFOLDING ROADMAP
- **Phase 1: Workspace & Root Config**: Initialize package manager, monorepo configuration (`turbo.json`, `tsconfig.base.json`, `package.json`).
- **Phase 2: Database Schema & Client**: Set up the data layer (S3, Azure Blob Storage, Google Cloud Storage, Event notification targets): client, connection pool, models, and migration scripts.
- **Phase 3: Design Tokens & UI Primitives**: Build accessible `Button`, `Input`, `Card`, `Badge`, and layout wrappers inside `packages/ui`.
- **Phase 4: Core Application Routes & Handlers**: Implement primary authentication, user session handling, and application routes.
- **Phase 5: Quality Assurance & Build Verification**: Run `tsc --noEmit`, ESLint, Prettier, and smoke test suites to ensure zero compilation or runtime errors.
---
## 6. EXECUTION INSTRUCTIONS
1. Review all specifications, architectural guardrails, and stack choices above.
2. Present the full monorepo directory tree structure.
3. Systematically generate the complete, production-ready codebase according to the 5-phase roadmap above — starting with the root workspace setup, followed by the database schema, UI design system package, and full-stack application routes until the repository is fully scaffolded and ready to run.