How ahsanu123/planerp works
Main Components
Frontend Layer:
• Angular SPA (spa directory)
• React SPA (spa_react directory)
• Both as they seem to be alternative frontends
• UI components and state management
API Layer:
• ASP.NET Core Backend (api directory)
• GraphQL endpoints
• REST Controllers
• OpenID Connect/OAuth authentication
Service Layer:
• Event Bus (RabbitMQ implementation)
• Authentication/Authorization service (learn-auth directory)
• File storage service
• PostgreSQL database service
Key Relationships to Highlight
a. Client-Server Communication:
• Frontend → API (HTTP/GraphQL)
• Authentication flows
• Real-time updates via event bus
b. Service Integration:
• API → Database
• API → Message Queue
• API → File Storage
• Authentication service interactions
Specific Implementation Details
Database:
• PostgreSQL with custom types
• Dapper for data access
• FluentMigrator for schema management
Authentication:
• OpenIddict implementation
• Custom identity providers
• Role-based access control
Event Processing:
• RabbitMQ message broker
• Event bus abstraction
• Integration events
[Frontend Layer]
Angular SPA ←→ React SPA
• ↓ ↓
[API Gateway Layer]
• REST/GraphQL APIs
• ↓ ↓
[Service Layer]
Auth Service Event Bus File Service
• ↓ ↓ ↓
[Data Layer]
• PostgreSQL Database
Additional Elements
Security Layer:
• OAuth2/OpenID Connect flows
• Identity provider integration
• Role-based access control
Deployment Components:
• Docker containers (shown from dockerfile directory)
• Service orchestration
• Infrastructure components