Design a Learning Management Platform
Design versioned course publishing, enrollment, lesson progress, assignment submission, grading, and durable learner history.
Problem statement
For this exercise, assume instructors build draft courses from lessons and assignments, then publish an immutable course version. Learners enroll in a published version, consume lesson content, record progress, submit assignment attempts before a deadline, and read released grades and feedback. Publishing a later version does not rewrite an active learner's completed work; an authorized instructor may explicitly migrate future content while preserving history. Exact enrollment, progress, and submission retries are harmless, and one submission attempt is graded at most once per grading version. Assume five million learners, 100,000 active courses, 50,000 progress events per second, p95 course reads below 300 milliseconds, and published content surviving one availability-zone failure. Live video delivery, payment collection, plagiarism detection, identity-provider implementation, and recommendation ranking are outside scope. The implementation stack is prescribed: MongoDB, Express.js, React, and Node.js. Treat those technologies as fixed constraints and explain the data, API, server-process, and client boundaries needed to preserve the behavioral contract.
What to build
- Instructors can edit drafts and atomically publish immutable course versions containing lessons and assignments.
- Learners can enroll in one published version and read authorized course content without later edits rewriting completed history.
- Learners can record lesson progress and submit retry-safe assignment attempts with explicit deadline and validation outcomes.
- Authorized graders can record and release one versioned grade and feedback result for an exact submission attempt.
At scale
- Five million learners, 100,000 active courses, and 50,000 progress events per second are authored practice assumptions.
- Healthy published-course reads complete below 300 milliseconds at p95.
- Published course content and accepted submissions survive one availability-zone failure.