LMS SaaS Platform
A polyglot-persistence, multi-tenant LMS engine shipped across four different UI stacks from one shared domain core.
A backend-first, Domain-Driven Design LMS platform built for enterprises and independent instructors, featuring an extensible question/grading engine, culture-aware localization, and a single Application/Domain core driving React, Blazor, MAUI, and Razor front ends simultaneously.
The Motivation
I wanted to prove that a single engineer could design an enterprise-grade multi-tenant SaaS backend the way a well-funded platform team would — proper Domain-Driven Design, polyglot persistence chosen per workload, and an extensibility model for grading and content — and then carry that same domain core across four completely different presentation stacks (React, Blazor, MAUI, and Razor) without forking business logic. It's as much a statement about architectural discipline as it is about full-stack range.
The Problem It Solves
Most learning platforms force a tradeoff: an off-the-shelf SaaS LMS that can't be extended with new question types, custom grading scales, or genuinely localized (not just translated) content, or a from-scratch build that reinvents multi-tenancy, grading, and event plumbing badly and only ships a single client. Enterprises and instructors needed a core that could grow new question types and integrations without touching the grading engine, and that could serve web, mobile, and admin surfaces from one source of truth.