Architecture Blueprint

How Stereoglam's ticketing platform is wired — services, infrastructure, and data flows.

00

System Context (C4)

High-level C4 context diagram showing the Stereoglam ticketing platform, its users, and external system dependencies

c4contextarchitecture
→
01

Infrastructure & Deployment Overview

GCP services, Cloud Run backends, data layer, frontends on Cloudflare, and all external service integrations

gcpcloud-runinfra
→
02

Component Diagram

All platform components organized by portal — Admin, Checkout, Core, Message Service, Report Exporter, Identity, and App

componentsportalsservices
→
03

Domain Contexts & Business Layer

Admin and Buyer bounded contexts with auth layer, API integrations, and data layer connections

dddcontextsbusiness-logic
→
04

Request Flow & Data Architecture

Sequence diagrams for authentication, data queries, checkout, and webhook processing

sequenceauthcheckoutwebhooks
→
05

Service Dependency Map

Which services are shared vs admin-only vs buyer-only across the platform

dependenciesservicesshared
→
06

Tech Stack Comparison

Side-by-side comparison of Stereoglam's modern stack versus FC's legacy architecture

comparisonarchitecture
→