Sentry

# MISSION: Scaffold "Sentry" 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 **Sentry**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Sentry
- **What It Does**: Sentry is an open-source application monitoring platform for real-time error tracking, performance tracing, session replay, and metrics.
- **Domain & Category**: Error Tracking Platform
- **Production Scale**: 20+ people
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Pairing Django with Kafka and ClickHouse allows Sentry to ingest billions of events daily while providing sub-second analytical search across production traces.
- **Live Website Reference**: https://sentry.io
- **Source Repository**: https://github.com/getsentry/sentry
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Python, Django, React, TypeScript, ClickHouse, PostgreSQL, Kafka, Redis, Celery
- **Primary Language(s)**: Python, TypeScript, MDX
- **License of the reference repo**: NOASSERTION
- **Frontend**: React — Drives the performance dashboards, issue stream explorer, and trace visualizer in static/app.; TypeScript — Enforces type safety across frontend application views, models, and API client types.; Emotion — CSS-in-JS styling library providing dynamic theme tokens and component styles.
- **Backend & APIs**: Python — Core backend runtime powering application endpoints, Celery workers, and event processing.; Django — Web framework serving the Sentry REST API, team permissions, and project configurations.; Celery — Distributed task queue managing asynchronous notifications, quotas, and digest delivery.
- **Data & persistence**: ClickHouse — Columnar storage backing Snuba for petabyte-scale event queries and trace analytics.; PostgreSQL — Primary relational database for projects, team memberships, user accounts, and auth tokens.; Kafka — Streaming message bus buffering incoming error events and telemetry between ingestion and storage.; Redis — High-speed cache for session states, rate limits, TSDB metric buffers, and Celery brokers.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/getsentry/sentry @ 45f1842)
1. **Bifurcated architecture: transactional Django core with Snuba/ClickHouse analytics**: Relational entities (organizations, projects, issue alert rules) reside in PostgreSQL via Django ORM, while raw crash events and performance spans route through Snuba into ClickHouse.
2. **Kafka streaming pipeline buffers high-velocity event ingestion**: Incoming crash reports from Sentry Relay proxies are queued into Apache Kafka topics before batch consumers perform deduplication, fingerprinting, and insertion into ClickHouse.
3. **Symbolication and native stacktrace processing offloaded to Rust microservices**: CPU-intensive debug symbol resolution (DWARF, dSYM, Proguard, Source maps) is delegated to specialized Rust services (Symbolicator, Relay) rather than blocking Python Django processes.
4. **Snuba query engine provides a unified analytical API abstraction**: Snuba sits in front of ClickHouse to parse structured analytical queries from Sentry, enforcing multi-tenant quotas, dataset aliases, and query optimizations automatically.
5. **Hierarchical Redis caching and rate-limiting buffers**: Redis buffers quota counters, rate limits, and short-lived session states, shielding PostgreSQL and Kafka from traffic bursts during severe production cascading outages.
---
## 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 (ClickHouse, PostgreSQL, Kafka, Redis): 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.