Architecture & Cross-Cutting Concerns¶
How the system is structured and how the cross-cutting mechanics (requests, auth, multi-tenancy, async jobs, real-time, integrations, security) work. For the per-feature views, see the feature docs. A legacy high-level overview also lives in system-design.md.
- System Context & Container Architecture (C4) — This is the entry-point architecture document for the MAS / Mr. Mentor backend. It explains, at a
- Request Lifecycle & Middleware Pipeline — This document is the canonical reference for how an HTTP request travels through the
- Multi-Platform / Multi-Tenant Architecture — How a single Express + TypeScript backend (mr-mentor-backend, port 8000) serves several brands and products at once — Mr. Mentor, My Analytics School (MAS), and the Mr. Hire HR portal — from one PostgreSQL database, one Redis/BullMQ…
- Background Jobs & Queues (Redis + BullMQ) — All work in the Mr. Mentor backend that must not block an HTTP request — sending email, AI resume screening,
- Real-time — Socket.IO, WebRTC Meetings & Terminal Relay — This document is the canonical reference for every real-time transport in the MAS / Mr. Mentor
- External Integrations Catalog — A single, source-cited catalog of every third-party (and cross-service) integration the mr-mentor-backend API talks to: what it does, the service/controller that wraps it, the env vars it reads, whether traffic is outbound (the API…
- Security & Authorization Architecture — This document is the canonical reference for how the Mr. Mentor / MAS backend authenticates callers, authorizes them against the role matrix, protects secrets, verifies inbound webhooks, and records security-relevant audit trails. It is…