How mattrathburn/gymhub works
Project type and purpose
• This is a full-stack, cloud-native microservices application (“Gym Hub”) for fitness-program subscription, built on .NET 8 with Clean Architecture and Vertical-Slice principles.
• It comprises multiple back-end services (APIs, event bus, DB manager), two client UIs (Blazor Admin and two WebApp flavors—Angular & React/Vite), plus infrastructure libraries.
File-structure highlights & architectural patterns
• src/EventBus + src/EventBusRabbitMQ: a shared abstraction layer and RabbitMQ/MassTransit integration for async, event-driven communication.
• GymHub.ServiceDefaults: common startup, swagger, authn/authz extensions used by all services.
• GymHub.AppHost: the host project orchestrating service registration (APIs, event bus, defaults).
• GH.Plan.API, Todo.API: vertical-slice microservices exposing REST endpoints, using EF Core migrations to PostgreSQL (and optionally SQL Server).
• GH.Plan.DbManager: a console or background service bootstrapping DB schemas/data.
• GH.Infrastructure & GH.Plan.Db: data models, DbContexts, repository implementations.
• GH.Admin (Blazor) and GH.WebApp (Angular + React/Vite): front-end clients consuming the APIs.
• Identity Server (implied by README): an authN/authZ microservice or external provider.