How dddwa/dddperth works
Main Components
a. Frontend Layer:
• Next.js/Remix Application (main website)
• UI Components (ParkUI framework)
• MDX Content Processing
• Client-side State Management
b. Backend Services:
• Server-side Rendering (SSR) Components
• API Integrations:
• EventsAir Integration
• Sessionize Integration
• Tito Integration (ticketing)
• GitHub Integration
c. Infrastructure:
• Azure Infrastructure (based on .bicep files)
• Container Registry
• Key Vault
• Monitoring Services
• Dashboard
d. Observability:
• OpenTelemetry Integration
• Jaeger Tracing
[Client Layer] → [Application Layer] → [Infrastructure Layer]
Specific Component Relationships
• Content Flow: website-content → MDX Compilation → Frontend Routes
• API Integrations: Show external service connections
• Monitoring Flow: Application → OpenTelemetry → Jaeger
• Infrastructure Dependencies: Show Azure resources relationships
Important Details
a. Frontend Architecture:
• Component hierarchy (header, footer, hero, UI components)
• Static content flow (blog, pages)
• Client-side entry points
b. Backend Services:
• Server-side functions
• API integration points
• Authentication/authorization flows
c. Infrastructure Components:
• Container deployment
• Key Vault secrets management
• Monitoring setup
• Static content delivery