SeaweedFS

# MISSION: Scaffold "SeaweedFS" 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 **SeaweedFS**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: SeaweedFS
- **What It Does**: SeaweedFS is a distributed object store, file system, and data lake storage engine designed to store billions of files with O(1) disk access.
- **Domain & Category**: Distributed Blob & File Storage
- **Production Scale**: 2-5 People
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Decoupling directory metadata from physical volume storage eliminates central metadata bottlenecks, enabling massive horizontal scaling for small and large files alike.
- **Live Website Reference**: https://seaweedfs.github.io
- **Source Repository**: https://github.com/seaweedfs/seaweedfs
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Go, Rust, Docker, Kubernetes, S3, RocksDB
- **Primary Language(s)**: Go, Rust
- **License of the reference repo**: Apache-2.0
- **Backend & APIs**: Go — Core systems language powering the Master, Filer, and Volume server daemons in go.mod.; Rust — High-performance native volume server engine implemented in seaweed-volume/Cargo.toml.
- **Data & persistence**: S3 — S3-compatible object storage API layer supporting buckets, multipart uploads, and lifecycle rules.; RocksDB — High-speed embedded key-value store used as the default metadata engine for Filer nodes.
- **Infrastructure & deploy**: Docker — Docker Compose orchestration environments in docker/compose for multi-node clusters.; Kubernetes — Production Kubernetes Helm charts in k8s/charts for scalable volume and master daemon sets.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/seaweedfs/seaweedfs @ 66f1754)
1. **Haystack-inspired architecture: decoupling metadata from chunk storage**: SeaweedFS separates directory metadata (Filer) from binary blob storage (Volume Servers). Master nodes maintain volume layouts via Raft, while Volume servers store raw file chunks in append-only files with O(1) disk lookups.
2. **Pluggable Filer metadata backends (RocksDB, PostgreSQL, FoundationDB)**: The Filer layer supports swappable metadata stores configured in filer.toml (RocksDB for single-node, PostgreSQL or FoundationDB for distributed metadata), allowing scaling from embedded servers to multi-terabyte directories.
3. **Native S3 and POSIX FUSE filesystem interfaces**: SeaweedFS natively presents data as S3 object buckets, POSIX file mounts via FUSE, Hadoop HDFS-compatible file systems, and WebDAV endpoints without requiring third-party translation proxies.
4. **Erasure coding for cold storage space efficiency**: To reduce hardware storage costs, older volume files can be encoded using Reed-Solomon erasure coding (8+4 or 10+4), reducing replication overhead from 3x to 1.3x while maintaining fault tolerance.
5. **Rust volume server rewrite for zero-overhead disk I/O**: The seaweed-volume project (seaweed-volume/Cargo.toml) ports the disk I/O intensive volume daemon to Rust, eliminating Go GC pauses and optimizing kernel page cache interactions.
---
## 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, RocksDB): 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.