A decade-old VB.NET monolith, rebuilt on .NET 8 and React
This application modernization case study covers an Environmental Health & Safety (EHS) platform used across global industrial operations. The client ran a decade-old VB.NET monolith with deeply coupled modules, and it had to work for multiple regions and languages. We rebuilt it as a modular .NET 8 API with a React front end, one module at a time, running alongside the legacy app. It was delivered as a phased rollout.
| Before | After | |
|---|---|---|
| Architecture | Monolith with deeply coupled modules | Modular .NET 8 API: Controllers, Services, Repositories |
| Front end | Decade-old VB.NET application | React single-page app with i18n |
| Scheduled tasks | Legacy scheduled tasks | Hangfire recurring and on-demand jobs in a separate Scheduler service |
| Server logic | Stateful, server-side | Stateless REST APIs |
| Access control | Needed granular control | Policy-based authorization with JWT Bearer, Basic and API Key schemes |
| Live updates | Needed for data-heavy dashboards | SignalR hubs and Firebase push notifications |
| Languages | Needed across regions | Runtime locale switching |
We used a strangler-fig approach. The new .NET 8 APIs ran in parallel with the legacy app while legacy logic was retired module by module, starting with Auth, then MOC, then Events.
A modular .NET 8 backend replaced the coupled monolith, aimed at global operations.
Clear layers, tests for each controller and service, and one module rebuilt at a time.
Stateless REST APIs and real-time updates for data-intensive dashboards.
New APIs ran in parallel with the legacy app while legacy logic was retired.
Policy-based authorization, three authentication schemes and secure configuration and secret management.
Elasticsearch logging and Hangfire monitoring dashboards were set up as part of the work.
We moved a decade-old VB.NET monolith to a modular .NET 8 / ASP.NET Core Web API with a React front end. A separate Hangfire Scheduler service replaced the legacy scheduled tasks.
We used a strangler-fig approach. The new APIs ran in parallel with the legacy app, and modules were rebuilt one at a time, starting with Auth, then MOC, then Events. Feature flags supported the phased rollout.
Maintaining zero downtime was a stated goal of the phased rollout. We haven't got a confirmed result to report on it.
Tell us about the application. We'll map its modules to API boundaries and show you how a phased rollout could run.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
Talk to a QServices solutions architect about your ERP. You'll leave with two or three automation ideas you can act on, even if you never work with us.