sentry-architecture-variants

# Sentry Architecture Variants ## Overview Choose the right Sentry SDK, project layout, and tracing strategy for each application architecture. Every pattern below uses Sentry SDK v8 APIs — `@sentry/node`, `@sentry/browser`, `@sentry/react`, `@sentry/react-native`, `@sentry/aws-serverless`, and `@sentry/google-cloud-serverless`. The goal is one coherent trace from the user's device through every backend hop, regardless of how many runtimes or deployment targets sit in between. Deep-dive references for each pattern: [Monolith](references/monolith-architecture.md) | [Microservices](references/microservices-architecture.md) | [Serverless](references/serverless-architecture.md) | [Event-driven](references/event-driven-architecture.md) | [Frontend SPA](references/frontend-spa-architecture.md) | [Mobile](references/mobile-architecture.md) | [Hybrid](references/hybrid-architecture.md) | [Errors](references/errors.md) ## Prerequisites - Node.js 18+ (or target platform runtime) - Sentry organization with at least one project created at [sentry.io](https://sentry.io) - `SENTRY_DSN` available as an environment variable (one per Sentry project) - Application architecture documented — service inventory, deployment targets, team ownership mapped - For distributed tracing: all inter-service transports identified (HTTP, gRPC, Kafka, SQS) ## Instructions ### Step 1 — Identify Your Architecture and Select SDK Packages Map every runtime in your system to the correct Sentry SDK package a...