# iedcmec/techno-event-management architecture

> Architecture diagram of the GitHub repository iedcmec/techno-event-management, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-25). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/iedcmec/techno-event-management
- Repository: https://github.com/iedcmec/techno-event-management

## Overview

##### Project Type and Purpose
- Techno Event Management is a full-stack, microservices-style event management suite. It provides:
- A multi-tenant web application for event organizers (apps/web-admin, Next.js on Vercel)
- A registration kiosk UI (apps/registration-admin, Vite + React)
- Several backend services (apps/core-admin, apps/core-auth0-actions, apps/core-mailer)
- Shared libraries and database migrations in a pnpm workspace

##### File-Structure Analysis
- Top-level: monorepo managed by pnpm & Turborepo (pnpm-workspace.yaml, turbo.json).
- apps/
- core-admin: primary REST API service (Node.js, Express/Koa style) handling events, participants, orgs. Uses Supabase utils & Prisma.
- core-auth0-actions: Auth0 Actions extension hooking into Auth0 flows (new-user hook).
- core-mailer: email service (NodeMailer + Redis) for transactional emails and QR code dispatch.
- web-admin: Next.js frontend for organizers (SSR & client features), using Prisma + API.
- registration-admin: client-side React/Vite SPA for public registration.
- packages/
- database: Prisma schema & migrations, shared client for services.
- auth0-flows: utilities for Auth0-DB integration.
- other config packages: tsconfig, eslint rules.

##### Key Architecture Insights from README
- Real-time participant tracking via QR codes.
- Analytics dashboard.
- Deployment allows running frontends and backends separately or together.

A. Frontends
1. Web-Admin (Next.js)
2. Registration-Admin (Vite/React SPA)
B. Backends (Dockerized microservices)
1. Core-Admin API
2. Core-Auth0-Actions service
3. Core-Mailer service
C. Data Stores & External Services
1. Supabase (Postgres + Auth)
2. Redis (for mailer queue)
3. Auth0 tenant (authentication & hooks)
4. External SMTP (NodeMailer)
D. Shared Libraries
- Packages/database (Prisma client)
- Packages/auth0-flows

##### Component Interactions
- Web-Admin & Registration-Admin → HTTP(S) → Core-Admin API
- Core-Admin ↔ Supabase (Postgres) via Prisma & supabase utils
- Core-Auth0-Actions invoked by Auth0 on user events → writes to Postgres via Packages/database
- Core-Mailer subscribes to Redis queue for email tasks → sends via NodeMailer/SMTP
- Web-Admin uses Auth0 for SSO; tokens validated by core-admin middleware
- Shared libraries packaged and versioned within pnpm workspace

##### Architectural Patterns & Principles
- Microservices: each backend service in its own Docker container
- Monorepo & Turborepo: code sharing and orchestrated builds
- API-First design: REST controllers in core-admin
- Event-driven/email queue: core-mailer consumes Redis jobs
- Externalized auth: Auth0 for identity, actions for custom logic
- CI/CD via GitHub Actions, containerization with Docker

##### Step-by-Step Creation
8. Three backends under “Docker Swarm / Kubernetes” boundary.
9. Shared library usage in a corner, showing “packages/database” imported by core-admin & core-auth0-actions.

##### Detail
- Every microservice, external dependency, and data flow.

## Diagram (Mermaid)

```mermaid
flowchart TD
    User[/“User”/] --> WebAdmin["Next.js Web-Admin"]:::frontend
    User --> RegAdmin["Registration-Admin (React/Vite)"]:::frontend

    subgraph "Frontends"
        WebAdmin
        RegAdmin
    end

    subgraph "Backend Microservices"
        CoreAdmin["Core-Admin API"]:::backend
        CoreAuth0["Core-Auth0-Actions"]:::backend
        CoreMailer["Core-Mailer Service"]:::backend
    end

    subgraph "Datastores & Queues"
        Postgres[(Postgres DB)]:::database
        RedisQ[(Redis Queue)]:::queue
    end

    Auth0Cloud["Auth0 Tenant"]:::external
    SMTPCloud["SMTP Service"]:::external

    subgraph "Shared Libraries"
        DBPkg["packages/database"]:::library
        Auth0Pkg["packages/auth0-flows"]:::library
    end

    WebAdmin -->|SSO Login| Auth0Cloud
    WebAdmin -->|REST calls| CoreAdmin
    RegAdmin -->|REST calls| CoreAdmin

    Auth0Cloud -->|Triggers Actions| CoreAuth0
    CoreAuth0 -->|Prisma & DB Writes| Postgres

    CoreAdmin -->|Prisma/Supabase SDK| Postgres
    CoreAdmin -->|Enqueue email job| RedisQ

    RedisQ -->|Consume jobs| CoreMailer
    CoreMailer -->|Send emails| SMTPCloud

    DBPkg --> CoreAdmin
    DBPkg --> CoreAuth0
    Auth0Pkg --> CoreAuth0

    click WebAdmin "https://github.com/iedcmec/techno-event-management/tree/main/apps/web-admin"
    click RegAdmin "https://github.com/iedcmec/techno-event-management/tree/main/apps/registration-admin"
    click CoreAdmin "https://github.com/iedcmec/techno-event-management/tree/main/apps/core-admin"
    click CoreAuth0 "https://github.com/iedcmec/techno-event-management/tree/main/apps/core-auth0-actions"
    click CoreMailer "https://github.com/iedcmec/techno-event-management/tree/main/apps/core-mailer"
    click DBPkg "https://github.com/iedcmec/techno-event-management/tree/main/packages/database"
    click Auth0Pkg "https://github.com/iedcmec/techno-event-management/tree/main/packages/auth0-flows"

    classDef frontend fill:#D0E8FF,stroke:#0366d6
    classDef backend fill:#D0FFD8,stroke:#22863a
    classDef database fill:#FFFBBD,stroke:#FFD33D
    classDef queue fill:#FFEBE5,stroke:#CB2431
    classDef external fill:#F0F0F0,stroke:#6A737D
    classDef library fill:#FFF5B1,stroke:#C49000
```
