| Stack | Role | Year | Status |
|---|---|---|---|
| React, TypeScript, Django, Django REST Framework, PostgreSQL, JWT, Tailwind CSS, Axios | Full-Stack Software Engineer | 2024 | Live |

E-Learning Platform - Scalable Learning Management System
Building a comprehensive e-learning platform with Django and React
A learning management system with a Django REST Framework backend and a React and TypeScript frontend. It covers courses, enrollment, progress tracking and analytics, on a PostgreSQL schema designed for efficient queries.
The Problem
Educational institutions require scalable platforms to deliver online courses, but existing solutions are either cost-prohibitive or lack the flexibility for custom requirements. Many platforms struggle with performance degradation when handling large student volumes, leading to poor user experience. Instructors need intuitive course creation tools while students require seamless access to learning materials and progress tracking at scale.
To get control over the data model without vendor lock-in, I built a custom LMS with a clear separation between API and frontend, so a failure in one layer does not bring down the other.
The Solution
I built a custom e-learning platform using Django REST Framework for the backend services and React with TypeScript for the frontend. The data model uses indexed PostgreSQL queries and ORM query optimisation to keep course and enrollment pages efficient, and stateless JWT authentication keeps the API simple to scale horizontally.
Key Technical Terms
- select_related / prefetch_related:In this LMS, Django ORM uses these to fetch courses, lessons and enrollments in fewer queries; which cuts N+1 round-trips and keeps course pages efficient.
- JWT refresh token rotation:Tokens are rotated on refresh so a stolen refresh token has a short window; this keeps authentication stateless for horizontal scaling while improving security for student and instructor accounts.
- Stateless API:The Django backend does not store session state; every request carries identity and context so we can add more app servers behind a load balancer without sticky sessions, which keeps horizontal scaling straightforward.
The Impact
The platform gives instructors and students a working course, enrollment and progress system. Its architecture is designed for efficient queries and horizontal scaling, but it has not been load-tested, so no capacity or uptime figures are claimed.
Django REST
PostgreSQL
Stateless JWT
React + TypeScript
Outcomes
- Working course management, enrollment and progress tracking
- Query optimisation with select_related, prefetch_related and indexes to avoid N+1 queries
- Stateless JWT authentication that suits horizontal scaling
- Analytics for instructors and students
- Deployed on Netlify and Render with a PostgreSQL database
Architecture Deep-Dive
The system follows a layered architecture with Django REST Framework backend and React frontend. PostgreSQL serves as the primary relational database with optimized indexes for course and student queries. Django ORM uses select_related and prefetch_related to minimize database roundtrips. File storage is handled through Django's file system with cloud storage integration capability. The frontend uses React Query for efficient data fetching and caching, reducing repeated API calls. Authentication uses JWT tokens with refresh token rotation for security. The architecture supports horizontal scaling through Django's stateless design and PostgreSQL read replicas.
Key Engineering Decisions
I chose Django over Node.js because the built-in admin and ORM accelerated development and gave instructors a ready-made back office, trading some raw performance for delivery speed. I selected PostgreSQL over MongoDB because course and enrollment data is relational and we needed complex queries and data integrity. I implemented API-first and deferred full SSR because we prioritized clear backend boundaries and faster iteration. I used JWT over session-based auth because stateless tokens let us scale app servers without shared session store. I deferred video streaming optimization to focus on core course delivery, with CDN integration planned for scaling.
Failure Modes & Resilience
Database overload: connection pooling and query optimization (select_related/prefetch_related) limit load; read replicas planned for scaling. File upload failures: handled asynchronously so a large lesson upload does not block the API; retries and user feedback on failure. Auth token expiry: refresh rotation and clear client-side handling so users are re-authenticated without losing context. Frontend errors: error boundaries prevent one broken course page from taking down the whole app.
Outcome & Future Potential
The platform gives instructors and students a working course, enrollment and progress system. Its architecture is designed for efficient queries and horizontal scaling, but it has not been load-tested, so no capacity or uptime figures are claimed.
Roadmap & Expansion
Future work could include Redis caching for frequently accessed courses, CDN integration for video and asset delivery and microservices extraction for video processing and analytics. Planned containerization with Docker for consistent deployments. Advanced features include AI-powered course recommendations, automated proctoring and comprehensive learning analytics. Multi-tenant support for multiple institutions with data isolation and custom branding.
Django REST
REST API with serializers and permission classes
PostgreSQL
Indexed queries for course and student data
Stateless JWT
No server-side session state to replicate
React + TypeScript
Typed UI separated from the API
Project Gallery
