Skip to content
MEMohan E

Loading portfolio

0%

MEMohan E

System Design

Architecture you can walk through in an interview

Replace diagram placeholders with exported visuals or interactive embeds when ready. The structure below is intentional for EM/architect conversations.

Authentication Flow

JWT-based login, claim validation, and RBAC enforcement across services.

[Architecture Diagram]

Nodes

Client→Auth API→User Store→Redis (optional revoke)→Protected Services
  1. 1User submits credentials
  2. 2Auth API verifies identity and issues JWT with role claims
  3. 3Client sends Bearer token on subsequent requests
  4. 4Services validate signature/expiry and enforce permissions

AI Pipeline

End-to-end path from user query to grounded streamed response.

[Architecture Diagram]

Nodes

Client→API Gateway / FastAPI→Embedder→Qdrant→LLM (Ollama)→Redis Memory
  1. 1Receive authenticated query
  2. 2Embed query and retrieve top-k chunks
  3. 3Assemble prompt with policies + context + memory
  4. 4Stream tokens to client

Material Processing

Upload to searchable knowledge via extraction and embeddings.

[Architecture Diagram]

Nodes

Upload API→Object Storage→Queue→OCR/PDF/Video Workers→DB→Qdrant
  1. 1Validate and store raw material
  2. 2Enqueue processing job
  3. 3Extract normalized text + metadata
  4. 4Chunk, embed, and upsert vectors

Microservices Boundaries

Separation between core domain systems and AI/worker services.

[Architecture Diagram]

Nodes

LMS/ERP (PHP)→AI Services (FastAPI)→Workers→Shared Data Stores→Frontends
  1. 1Core domain owns transactions and institutional workflows
  2. 2AI services own retrieval/generation contracts
  3. 3Workers handle async extraction and embedding

Deployment Architecture

Containerized services with environment-based configuration.

[Architecture Diagram]

Nodes

Docker Host→App Containers→AI Containers→DB/Redis/Qdrant→Reverse Proxy
  1. 1Build images per service
  2. 2Inject secrets/config via environment
  3. 3Route traffic through reverse proxy
  4. 4Observe logs and health endpoints

Database Architecture

Relational state, cache, and vector store responsibilities.

[Architecture Diagram]

Nodes

MySQL/PostgreSQL→Redis→Qdrant→Application Services
  1. 1Transactional entities in relational DB
  2. 2Ephemeral session/cache in Redis
  3. 3Semantic payloads and vectors in Qdrant

Request Flow

Typical authenticated API request lifecycle.

[Architecture Diagram]

Nodes

Client→Gateway→Auth Middleware→Controller/Service→Data Stores
  1. 1Authenticate and authorize
  2. 2Validate payload
  3. 3Execute business logic
  4. 4Persist/read and return response

API Flow

REST contract patterns between Vue clients and backend services.

[Architecture Diagram]

Nodes

Vue.js Client→REST Endpoints→Domain Services→AI Services
  1. 1UI calls versioned REST endpoints
  2. 2Domain APIs handle institutional workflows
  3. 3AI APIs handle chat/generation/retrieval

Question Generation Pipeline

From materials to validated assessment candidates.

[Architecture Diagram]

Nodes

Materials→Retrieval→Generator→Validator→Planner UI→Question Bank
  1. 1Retrieve concept context from materials
  2. 2Generate candidate questions
  3. 3Validate structure and detect duplicates
  4. 4Faculty reviews in planner before publish

Student Journey

Learner path through dashboard, materials, and AI assistance.

[Architecture Diagram]

Nodes

Login→Student Dashboard→Materials→AI Tutor→Assessments
  1. 1Authenticate as student
  2. 2View courses and materials
  3. 3Ask grounded questions via AI tutor
  4. 4Complete assessments and track progress

Admin Journey

Operator path for configuration, monitoring, and control.

[Architecture Diagram]

Nodes

Login→Admin Dashboard→Users/Roles→Content Ops→Analytics
  1. 1Authenticate with privileged role
  2. 2Manage users and permissions
  3. 3Monitor processing and AI usage
  4. 4Review operational reports