# wibu009/evently architecture

> Architecture diagram of the GitHub repository wibu009/evently, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-02-05). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/wibu009/evently
- Repository: https://github.com/wibu009/evently

## Overview

##### Project type and purpose
- Evently is a .NET 9–based, modular event management system demonstrating a hybrid between a Modular Monolith and Microservices architecture.
- Core modules (Users, Events, Attendance) run inside a single ASP.NET Core monolith (Evently.Api), while the Ticketing module has been extracted into its own microservice (Evently.Ticketing.Api).
- It follows Clean Architecture and DDD, uses CQRS (MediatR), and implements event‐driven integration (RabbitMQ, Outbox/Inbox) plus sagas.

##### File structure
- **src/API**:
- Evently.Api – the monolithic HTTP API exposing Users, Events, Attendance endpoints
- Evently.Gateway – YARP-based reverse proxy routing external requests
- Evently.Ticketing.Api – standalone Ticketing microservice API
- **src/Common**: shared libraries (Application, Domain, Infrastructure, Presentation) used by all modules
- **src/Modules/{Attendance,Events,Ticketing,Users}**: each with subfolders
- Application (commands/queries, MediatR pipeline behaviors)
- Domain (entities, aggregates, repository interfaces, domain events)
- Infrastructure (EF Core DbContexts, repositories, Outbox/Inbox, integration‐job configuration)
- IntegrationEvents (message contracts)
- Presentation (Minimal API endpoints, integration‐event handlers)
- **test/**: architectural tests, unit tests, integration tests across modules and end‐to‐end

##### README for additional insights
- Databases: PostgreSQL (write models per module), MongoDB (read models)
- Message broker: RabbitMQ via MassTransit
- Cache: Redis hybrid caching
- Identity: Keycloak
- Background jobs: Quartz.NET (process Outbox/Inbox jobs)
- Observability: OpenTelemetry, Jaeger, Seq
- API docs: Scalar
- Patterns: Clean Architecture, DDD, CQRS, Event‐Driven, Outbox/Inbox, Saga

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Clients and Entry
    Client["Client (SPA/API)"]:::external
    Gateway["API Gateway (YARP)"]:::gateway
    Client -->|"HTTP"| Gateway

    %% Services
    subgraph "Services Layer"
        direction TB
        MonolithService["Evently.Api Monolith"]:::serviceMono
        TicketService["Evently.Ticketing.Api"]:::serviceMicro
    end

    Gateway -->|"Routes"| MonolithService
    Gateway -->|"Routes"| TicketService

    %% Monolith Modules
    subgraph "Monolith Modules" 
        direction TB
        UsersModule["Users Module"]:::moduleMono
        EventsModule["Events Module"]:::moduleMono
        AttendanceModule["Attendance Module"]:::moduleMono
    end
    MonolithService --> UsersModule
    MonolithService --> EventsModule
    MonolithService --> AttendanceModule

    %% Ticketing Module
    TicketModule["Ticketing Module"]:::moduleMicro
    TicketService --> TicketModule

    %% Databases Write Stores
    subgraph "PostgreSQL Write Stores"
        direction TB
        UsersDB["UsersDbContext"]:::db
        EventsDB["EventsDbContext"]:::db
        AttendanceDB["AttendanceDbContext"]:::db
        TicketingDB["TicketingDbContext"]:::db
    end

    UsersModule -->|"Reads/Writes"| UsersDB
    EventsModule -->|"Reads/Writes"| EventsDB
    AttendanceModule -->|"Reads/Writes"| AttendanceDB
    TicketModule -->|"Reads/Writes"| TicketingDB

    %% Read Store
    Mongo["MongoDB Read Store"]:::db
    UsersModule -->|"Updates"| Mongo
    EventsModule -->|"Updates"| Mongo
    AttendanceModule -->|"Updates"| Mongo
    TicketModule -->|"Updates"| Mongo

    %% Messaging
    Rabbit["RabbitMQ"]:::message
    UsersModule -.->|"Outbox Events"| Rabbit
    EventsModule -.->|"Outbox Events"| Rabbit
    AttendanceModule -.->|"Outbox Events"| Rabbit
    TicketModule -.->|"Outbox Events"| Rabbit

    Rabbit -.->|"Inbox Consumers"| UsersModule
    Rabbit -.->|"Inbox Consumers"| EventsModule
    Rabbit -.->|"Inbox Consumers"| AttendanceModule
    Rabbit -.->|"Inbox Consumers"| TicketModule

    %% Caching, Identity, Scheduler
    Redis["Redis Cache"]:::external
    Keycloak["Keycloak"]:::external
    Quartz["Quartz.NET Scheduler"]:::external

    UsersModule -->|"Auth"| Keycloak
    EventsModule -->|"Auth"| Keycloak
    AttendanceModule -->|"Auth"| Keycloak
    TicketModule -->|"Auth"| Keycloak

    AttendanceModule -->|"Cache"| Redis
    EventsModule -->|"Cache"| Redis
    UsersModule -->|"Cache"| Redis
    TicketModule -->|"Cache"| Redis

    Quartz -.->|"Triggers Outbox Processing"| UsersModule
    Quartz -.->|"Triggers Outbox Processing"| EventsModule
    Quartz -.->|"Triggers Outbox Processing"| AttendanceModule
    Quartz -.->|"Triggers Outbox Processing"| TicketModule

    %% Observability
    subgraph "Observability Stack"
        direction TB
        OTEL["OpenTelemetry"]:::external
        Jaeger["Jaeger"]:::external
        Seq["Seq"]:::external
    end
    MonolithService --> OTEL
    TicketService --> OTEL
    OTEL --> Jaeger
    MonolithService --> Seq
    TicketService --> Seq

    %% Click Events
    click Gateway "https://github.com/wibu009/evently/blob/main/src/API/Evently.Gateway"
    click MonolithService "https://github.com/wibu009/evently/blob/main/src/API/Evently.Api"
    click TicketService "https://github.com/wibu009/evently/blob/main/src/API/Evently.Ticketing.Api"
    click UsersModule "https://github.com/wibu009/evently/blob/main/src/Modules/Users/Evently.Modules.Users.Application"
    click EventsModule "https://github.com/wibu009/evently/blob/main/src/Modules/Events/Evently.Modules.Events.Application"
    click AttendanceModule "https://github.com/wibu009/evently/blob/main/src/Modules/Attendance/Evently.Modules.Attendance.Application"
    click TicketModule "https://github.com/wibu009/evently/blob/main/src/Modules/Ticketing/Evently.Modules.Ticketing.Application"
    click UsersDB "https://github.com/wibu009/evently/blob/main/src/Modules/Users/Evently.Modules.Users.Infrastructure/Database/UsersDbContext.cs"
    click EventsDB "https://github.com/wibu009/evently/blob/main/src/Modules/Events/Evently.Modules.Events.Infrastructure/Database/EventsDbContext.cs"
    click AttendanceDB "https://github.com/wibu009/evently/blob/main/src/Modules/Attendance/Evently.Modules.Attendance.Infrastructure/Database/AttendanceDbContext.cs"
    click TicketingDB "https://github.com/wibu009/evently/blob/main/src/Modules/Ticketing/Evently.Modules.Ticketing.Infrastructure/Database/TicketingDbContext.cs"
    click Rabbit "https://github.com/wibu009/evently/blob/main/src/Common/Evently.Common.Infrastructure/EventBus/EventBus.cs"
    click Quartz "https://github.com/wibu009/evently/blob/main/src/Modules/Ticketing/Evently.Modules.Ticketing.Infrastructure/Outbox/ProcessOutboxJob.cs"
    click Keycloak "https://github.com/wibu009/evently/blob/main/src/Modules/Users/Evently.Modules.Users.Infrastructure/Identity/KeyCloakClient.cs"

    %% Styles
    classDef serviceMono fill:#AEDFF7,stroke:#0366d6,color:#000;
    classDef serviceMicro fill:#F7D6AE,stroke:#d66303,color:#000;
    classDef moduleMono fill:#D6EAF8,stroke:#2E86C1,color:#000;
    classDef moduleMicro fill:#FDEBD0,stroke:#D35400,color:#000;
    classDef db fill:#D5F5E3,stroke:#27AE60,color:#000,shape:cylinder;
    classDef message fill:#FEF9E7,stroke:#F1C40F,color:#000,shape:cloud;
    classDef external fill:#E8E8E8,stroke:#7F8C8D,color:#000;
    classDef gateway fill:#D5DBDB,stroke:#566573,color:#000;
    classDef serviceMono,serviceMicro moduleMono,moduleMicro;
    classDef OTEL,Jaeger,Seq external;
    classDef Redis,Keycloak,Quartz external;
```
