Modernising to .NET Core and Blazor

Improving scalability without stopping delivery

Migrated applications onto .NET Core and Blazor Server to improve scalability and performance, sequenced so feature delivery continued throughout.

Cloud and Platform, 2021-Present, nimbus Cloud

The problem

A platform on an older framework accumulates a specific kind of cost. Hosting options narrow, performance work hits a ceiling you cannot raise, and the gap between the platform and the ecosystem around it widens every year.

The obvious answer is a rewrite, and the obvious answer is usually wrong. A feature freeze long enough to rewrite a working product is rarely something a business can absorb.

The approach

Migrated onto .NET Core for the runtime and hosting improvements, and to Blazor Server on the front end so the team could work in one language across the stack rather than maintaining two skill sets.

Sequenced the migration so delivery continued alongside it. Modernisation that requires the business to stop is modernisation that gets cancelled halfway through.

Paired it with the infrastructure as code and automated deployment work, since a modernised application on a hand-built environment only solves half the problem.

The outcome

Scalability and performance improved on the migrated applications.

The team works in a single stack across front end and back end, which widened who can pick up a given piece of work.

.NET Core, Blazor Server, C#, Azure, Migration

Something went wrong. Reload 🗙