How We Refactored a Legacy E-Learning Platform for Scale

The organisation relied on a platform that had evolved over roughly two decades. It supported services ranging from preparatory courses to live state examinations, with millions of students and administrators depending on it during periods of high demand.

The key challenges included:

• Outdated .NET libraries and complex dependencies
• Performance lag, system crashes, and slow reporting
• A high-demand exam season with little tolerance for downtime
• Limited internal capacity for deeper modernisation work
• The need to improve stability without a disruptive full rewrite
• A longer-term plan to migrate the platform to AWS

The timing increased the operational risk. A high-demand exam season was approaching, and an outage could prevent students from accessing their examinations and disrupt schools and administrators. At the same time, the client's internal engineering team was already focused on day-to-day operational priorities.

The organisation needed to stabilise the existing platform before peak demand while creating a controlled path towards longer-term modernisation and AWS migration.

We modernised key parts of the existing platform, improving performance, maintainability, and efficiency without requiring a full rewrite.

LLI adopted an incremental modernisation approach, prioritising high-risk components while retaining stable parts of the platform.

This allowed selective refactoring and a gradual AWS migration, delivering immediate exam-season stability while advancing the long-term modernisation roadmap.

The system was improved with long-term maintainability in mind. Removing unnecessary dependencies and introducing more modular updates reduced the likelihood that a change in one area would create unintended effects elsewhere in the application.

Automated monitoring provided greater visibility into system behaviour and performance. This supported both day-to-day operation and future engineering work by making issues easier to identify and investigate.

LLI also worked directly with the client's internal team throughout the engagement. Engineering decisions remained connected to the organisation's operational priorities and longer-term infrastructure direction rather than being made as part of an isolated external rebuild.

Application modernisation does not always require a full rewrite or immediate migration. For organisations running critical legacy software, the more important question is often what needs to change first, what can safely remain, and how each step supports the target architecture.

This case reflects LLI's approach to Application Modernisation & Migration. We assess the existing environment, identify where technology is creating operational risk, and sequence the work around the priorities that matter most to the organisation.

Here, that meant stabilising a critical education platform before a high-demand examination period, while making deliberate changes that would also support a future AWS migration.

• The value: the organisation protected a critical operational period, improved the maintainability of its existing platform, and gained a controlled path towards cloud modernisation without forcing unnecessary large-scale change.