Full "ground-up" software rewrites almost always exceed their budget, miss delivery deadlines, and fail to replicate subtle business logic accumulated over years. The Strangler Fig migration pattern allows growing companies to replace legacy monoliths incrementally—carving off discrete domains into modern, type-safe services while maintaining continuous business operations.
The Fallacy of the Ground-Up Rewrite
When leadership decides to freeze existing software and spend twelve months rebuilding from scratch, the legacy system continues to evolve with emergency bug fixes and new market requirements. The new rewrite ends up chasing a moving target.
Instead of halting progress, an edge proxy (such as Cloudflare Workers or an API Gateway) routes traffic dynamically: high-value features are served by modern Next.js/Node microservices, while legacy flows continue running unchanged behind the scenes.
Incremental API Facades and Edge Routing
By placing a unified TypeScript API gateway between client applications and legacy services, frontend teams can immediately build clean modern user interfaces without being constrained by legacy database layouts.
As individual backend domains are refactored into high-speed PostgreSQL or microservices, the API gateway redirects requests without requiring mobile app updates or breaking third-party partner integrations.
// Edge Proxy Strangler Router
export default {
async fetch(request: Request, env: Env): Promise<Response> {
const url = new URL(request.url);
// Route modernized domains to the new Next.js platform
if (url.pathname.startsWith('/api/v2/checkout') || url.pathname.startsWith('/portal')) {
return fetch(`${env.MODERN_ORIGIN}${url.pathname}`, request);
}
// Pass legacy paths directly to legacy server cluster
return fetch(`${env.LEGACY_ORIGIN}${url.pathname}`, request);
},
};Key Engineering Takeaways
- Avoid high-risk ground-up rewrites by adopting the incremental Strangler Fig pattern.
- Use edge API gateways to deliver immediate UX enhancements while modernizing backend systems.
- Preserve business continuity and active revenue generation during multi-month refactoring programs.