back to archive
case_study.mdOct 2025-Present
LMS Microservices Platform
Architected a scalable LMS using Node.js and TypeScript microservices, securing 10+ API endpoints via Kong API Gateway and HashiCorp Vault to support 1,000+ concurrent users.
Node.jsTypeScriptKafkaRedisKongVault
problem
A college-scale Learning Management System needs role-aware access (Dean, HOD, Faculty, Student), secrets that don't live in application config, and an event backbone that keeps enrollment, grading, and notification services in sync without tight coupling.
architecture decisions
- 01Node.js/TypeScript microservices behind Kong API Gateway, which centralizes routing, rate limiting, and auth enforcement instead of duplicating that logic in every service.
- 02HashiCorp Vault issues and rotates service credentials and API secrets, so no service ships a long-lived static secret.
- 03PASETO-based authentication with single-device-login enforcement, closing the session-replay gap that plain JWT-in-localStorage setups leave open.
- 04Kafka as the event bus between services (enrollment, grading, notifications) so a spike in one domain doesn't back-pressure the others synchronously.
- 05Redis for session/cache state shared across service instances, keeping the services themselves stateless and horizontally scalable.
my contribution
Owned the overall service architecture and the API gateway/Vault integration, and implemented the RBAC model spanning Dean, HOD, Faculty, and Student roles.