System Architecture

High-level architecture of the Prem Travels enterprise operations platform.

1. Four Foundational Layers

Layer 1 — Platform Core
Centralized notification engine, document lifecycle system, central bin (soft delete + recovery). Event-driven, AWS-triggered.

Layer 2 — Governance & Control Plane
Central role & permission engine, route- and API-level access control, policy-driven enforcement, multi-step auth (OTP, SMS, email).

Layer 3 — Operational Modules
HR, attendance & payroll; fleet, maintenance & work orders; driver & field applications. Policy-capable, deep verticals.

Layer 4 — User-Facing Applications
Admin, Driver, Employee, Customer, Vendor portals — tailored experiences on a single platform.

2. Core Components (Logical View)

┌─────────────────────────────────────────────────────────────────┐
│                     User-Facing Applications                      │
│   Admin Portal │ Driver App │ Employee Portal │ Customer │ Vendor │
└─────────────────────────────────┬───────────────────────────────┘
                                  │
┌─────────────────────────────────▼───────────────────────────────┐
│                      API / Backend Server                         │
│   REST APIs │ Auth │ RBAC │ Workflow Engine │ Business Logic    │
└─────────────────────────────────┬───────────────────────────────┘
                                  │
        ┌─────────────────────────┼─────────────────────────┐
        │                         │                         │
┌───────▼───────┐    ┌───────────▼───────────┐   ┌───────▼───────┐
│   Database    │    │   AWS EventBridge      │   │  Notifications │
│   (Primary)   │    │   (Event-driven)       │   │  SMS / Email   │
└───────────────┘    └───────────────────────┘   └───────────────┘

3. Tech Stack (Summary)

Frontend: React-based portals (Admin, Driver, Employee, Customer, Vendor), responsive/PWA where applicable.
Backend: Node.js server, REST APIs, role- and permission-based access control.
Data: Primary database for entities, audit trails, workflow state.
Events: AWS EventBridge (or equivalent) for event-driven triggers (notifications, document expiry, workflows).
Integrations: SMS, email, file storage, and third-party services as required.

4. Deployment Overview

Applications are deployed per environment (e.g. production, staging). Admin and other portals are hosted on dedicated subdomains. Backend APIs are centralized; event-driven jobs and notifications run via cloud triggers.