Ageing platforms tend to struggle in the same ways: slow performance, expensive maintenance, and an inability to ship new features. Here's the approach we use to modernize them without disrupting the business that depends on them.

The Challenge

A typical case: the system is built on classic ASP and VB6 - technology that's increasingly difficult to maintain. Finding developers is nearly impossible, and every change carries risk. The business needs to modernize but can't afford downtime.

Our Approach: Strangler Fig Pattern

Instead of a risky big-bang rewrite, we used the strangler fig pattern. We built new microservices in .NET Core that gradually replaced legacy functionality. Both systems ran in parallel, with traffic gradually shifted to the new platform.

What good looks like

  • Noticeably faster application performance
  • Lower infrastructure and maintenance costs
  • No downtime during the migration itself
  • A modern codebase that developers actually want to work on
  • Deployments that move from occasional to on-demand

Lessons Learned

The biggest lesson: don't try to modernize everything at once. Start with high-value, low-risk components. Build confidence and momentum before tackling the core systems. And always maintain the ability to roll back.

← All insights
Explore the engineering services behind these ideas →