sentry-reference-architecture

# Sentry Reference Architecture ## Overview Enterprise Sentry architecture patterns for multi-service organizations. Covers centralized configuration, project topology, team-based alert routing, distributed tracing, error middleware, source map management, and a production-ready SentryService wrapper. ## Prerequisites - Sentry organization at [sentry.io](https://sentry.io) (Business plan+ for team features) - `@sentry/node` v8+ installed (`npm install @sentry/node @sentry/profiling-node`) - Service inventory and team ownership documented - Node.js 18+ (ESM and native fetch instrumentation) ## Instructions ### Step 1 — Project Structure Strategy **Pattern A: One Project Per Service (3+ services, recommended)** ``` Organization: acme-corp ├── Team: platform-eng │ ├── Project: api-gateway (Node/Express) │ ├── Project: auth-service (Node/Fastify) │ └── Project: user-service (Node/Express) ├── Team: payments │ ├── Project: payment-api (Node/Express) │ └── Project: billing-worker (Node worker) └── Team: frontend ├── Project: web-app (React/Next.js) └── Project: mobile-app (React Native) ``` Benefits: independent quotas, team-scoped alerts, per-service rate limits, isolated release tracking. **Pattern B: Shared Project (< 3 services, single team)** — one project with `Environment` tags (production/staging/dev). Simpler setup; outgrow when alert noise exceeds one team. ### Step 2 — Centralized Config Module Creat...