How georgidimitrovx/healthsphere works
HealthSphere is an early-stage health-service web application: its visible workflow is sign-in or sign-up from an Angular client, through a gateway, to an authentication service. The gateway also hosts middleware that checks tokens with the authentication service before allowing other requests. The authentication endpoints currently return sample tokens; the README names no further product capabilities. The client components and shared account types are represented, but their detailed templates and the gateway’s service-routing helper were not sampled.
Main entry points: GatewayController.cs Request gateway · app.component.ts Client requests · app-routing.module.ts Client routes · Program.cs Server setup
Components 13
Web client
- Client routes
healthsphere.client/src/app/app-routing.module.ts - Sign-in screen
healthsphere.client/src/app/sign-in/sign-in.component.ts - Sign-up screen
healthsphere.client/src/app/sign-up/sign-up.component.ts - Client requests
healthsphere.client/src/app/app.component.ts
API gateway
- Request gateway
HealthSphere.Server/Controllers/GatewayController.cs - Service routing
HealthSphere.Server/Helpers.cs - Token middleware
HealthSphere.Server/AuthenticationMiddleware.cs - Server setup
HealthSphere.Server/Program.cs
Authentication
- Auth setup
HealthSphere.AuthenticationService/Program.cs - Sign-in and sign-up
HealthSphere.AuthenticationService/API/Controllers/AuthenticationController.cs
Other components
- User
- Account types
HealthSphere.SharedKernel/Interfaces/AccountTypes.cs - Credentials DTO
HealthSphere.SharedKernel/DTOs/UserCredentialsDto.cs
Connections 12
- User → Client routes: navigates
- Client routes → Sign-in screen: routes to
- Client routes → Sign-up screen: routes to
- Client requests → Request gateway: posts credentials
- Client requests → Credentials DTO: uses
- Client requests → Account types: uses account types
- Server setup → Token middleware: installs
- Server setup → Request gateway: maps controllers
- Request gateway → Service routing: resolves service
- Request gateway → Sign-in and sign-up: forwards requests
- Token middleware → Auth setup: requests token validation
- Auth setup → Sign-in and sign-up: maps controllers