How wibu009/evently works
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