<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt" -->

---
title: The strangler fig pattern: modernizing without a...
description: A detailed guide to the strangler fig pattern for modernizing legacy systems capability by capability rather than through a big-bang rewrite. It covers how the...
canonical: https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The strangler fig pattern: modernizing without a big-bang rewrite | daily.dev
og:description: A detailed guide to the strangler fig pattern for modernizing legacy systems capability by capability rather than through a big-bang rewrite. It covers how the...
og:url: https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt
og:image: https://api.daily.dev/og/posts/Bji9LIxDT.png
og:image:alt: The strangler fig pattern: modernizing without a big-bang rewrite
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The strangler fig pattern: modernizing without a big-bang rewrite

**[Netguru](https://daily.dev/sources/netguru)** · 14 min read · 35 upvotes · 6 comments

## Summary

A detailed guide to the strangler fig pattern for modernizing legacy systems capability by capability rather than through a big-bang rewrite. It covers how the facade layer routes traffic, the tradeoffs between dual writes and change data capture for data ownership during migration overlap, how to choose which capability to strangle first, why migrations commonly stall around 80% completion, the real infrastructure and reconciliation costs of running two systems in parallel, when the pattern is a poor fit, and how to define when a migration is actually finished versus just feature-complete.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.netguru.com/blog/strangler-fig-pattern-guide>

## Questions this post answers

### What's the difference between dual writes and change data capture for keeping two systems in sync during a migration?

Dual writes push every update to both the legacy and new system from the application layer, which is simple to build but fails under load since a partial failure leaves one system ahead with no record of which is correct. Change data capture instead reads the legacy database's write-ahead log and replays changes asynchronously, decoupling the write path and typically introducing under a second of replication lag when properly tuned, versus minutes-long lag for polling-based approaches.

_Weighing dual writes against CDC for a live migration is exactly the kind of tradeoff daily.dev helps engineers research._

### Which capability should you strangle first when applying the strangler fig pattern?

Start with a capability that has the fewest upstream dependencies, a narrow write surface, is read-heavy, and sits behind an interface the facade can intercept without touching shared mutable state. Avoid picking the biggest, most painful module first, since it's usually wired into shared tables, batch jobs, and fields that other services depend on, forcing the hardest reconciliation work before the team has run the pattern once.

_Sequencing a monolith decomposition is easier when developers can pull in real architecture experience via daily.dev._

### Why do strangler fig migrations often stall before reaching completion?

Strangler migrations commonly stall around 80% done because the remaining slices are the ones nobody scoped upfront, such as batch jobs with undocumented side effects or reporting pipelines nobody owns, while the business has already banked the win from the flagship capability going live. The fix is funding migrations through decision gates tied to legacy retirement rather than to feature parity on the new system.

_Tracking why modernization projects stall helps teams planning a migration on daily.dev avoid the same trap._

## Community discussion

Top comments from developers on daily.dev.

**@l9521787** · 3 upvotes

> I love the strangler fig pattern, but it can be quite hard if the old code is too messed up and has terrible boundaries and side effects.

**@anarunje** · 0 upvotes

> We started but we never finished 🙈

**@ristotoldsep** · 0 upvotes

> The last 20% of a migration has a suspicious habit of becoming permanent.

**@agustinbarrientos** · 0 upvotes

> How would you undo a slice after the new system has accepted changes the old setup can't handle?

**@trevorsuna** · 0 upvotes

> The 80% stall is the part teams underestimate: the easy capabilities move first, while shared data and awkward edge cases remain. Defining deletion milestones, reconciliation ownership, and a deadline for shutting off each old path should be part of the migration plan from day one.

## Similar posts on daily.dev

- [Repay Tech Debt with the Strangler Fig Pattern](https://daily.dev/posts/repay-tech-debt-with-the-strangler-fig-pattern-z57wnfd3i) · RUBYLAND · 2 upvotes · 4 comments
- [Monolith to Service Architecture](https://daily.dev/posts/monolith-to-service-architecture-2izyvqort) · System Design Codex · 101 upvotes · 4 comments
- [Strangler Fig Pattern in C\#: Refactoring a Monolith to Microservices](https://daily.dev/posts/strangler-fig-pattern-in-c-refactoring-a-monolith-to-microservices-mpwi8kfwk) · We Are .NET · 12 upvotes · 1 comments
- [Redesign without fear](https://daily.dev/posts/redesign-without-fear-4bs4ays3m) · ploeh blog · 6 upvotes · 1 comments

---

Tags: [#microservices](https://daily.dev/tags/microservices), [#change-data-capture](https://daily.dev/tags/change-data-capture)

[View this post on daily.dev](https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The strangler fig pattern: modernizing without a big-bang rewrite","url":"https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt"},"datePublished":"2026-09-22T09:35:45.034Z","dateModified":"2026-09-22T09:36:07.833Z","description":"A detailed guide to the strangler fig pattern for modernizing legacy systems capability by capability rather than through a big-bang rewrite. It covers how the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5a415039677711ffb5f8995d7699eb1d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5a415039677711ffb5f8995d7699eb1d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Netguru","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Netguru","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/201e234294cb4132ab31418b7627dbab","url":"https://daily.dev/sources/netguru"},"commentCount":6,"discussionUrl":"https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":35},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":6}],"keywords":"microservices,change-data-capture","timeRequired":"PT14M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Netguru","item":"https://daily.dev/sources/netguru"},{"@type":"ListItem","position":3,"name":"The strangler fig pattern: modernizing without a big-bang rewrite"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt","comment":[{"@type":"Comment","text":"I love the strangler fig pattern, but it can be quite hard if the old code is too messed up and has terrible boundaries and side effects.","datePublished":"2026-09-22T14:37:08.448Z","url":"https://daily.dev/posts/Bji9LIxDT#c-qBUXxIvDd","author":{"@type":"Person","name":"l9521787","url":"https://daily.dev/l9521787","image":"https://lh3.googleusercontent.com/a/AAcHTteQ9_ph6p5v02nn2-faHYGHFOWnqVD1uRpitrcpGIoS=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"We started but we never finished 🙈","datePublished":"2026-09-23T14:37:45.724Z","url":"https://daily.dev/posts/Bji9LIxDT#c-oCMJ23Y6t","author":{"@type":"Person","name":"Ana Runje","url":"https://daily.dev/anarunje","image":"https://lh3.googleusercontent.com/a/ACg8ocIDcvLUYwuTB1k36PZ3ThI8nqlYAN_Ew9akcLliJLHUR6RIzOqlSg=s96-c"}},{"@type":"Comment","text":"The last 20% of a migration has a suspicious habit of becoming permanent.","datePublished":"2026-09-23T14:18:04.158Z","url":"https://daily.dev/posts/Bji9LIxDT#c-BI4Bzf9B6","author":{"@type":"Person","name":"Risto Tõldsep","url":"https://daily.dev/ristotoldsep","image":"https://lh3.googleusercontent.com/a/ACg8ocLDWc6mZn0JwNmXXw6WY0L_HJ6pegzRttooC5VgtXESHSj3MNYx=s96-c"}},{"@type":"Comment","text":"How would you undo a slice after the new system has accepted changes the old setup can’t handle?","datePublished":"2026-09-24T02:21:47.616Z","url":"https://daily.dev/posts/Bji9LIxDT#c-mPK0DnPH9","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}},{"@type":"Comment","text":"The 80% stall is the part teams underestimate: the easy capabilities move first, while shared data and awkward edge cases remain. Defining deletion milestones, reconciliation ownership, and a deadline for shutting off each old path should be part of the migration plan from day one.","datePublished":"2026-09-24T06:15:38.172Z","url":"https://daily.dev/posts/Bji9LIxDT#c-MQ1kht0I0","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-strangler-fig-pattern-modernizing-without-a-big-bang-rewrite-bji9lixdt#faq","mainEntity":[{"@type":"Question","name":"What's the difference between dual writes and change data capture for keeping two systems in sync during a migration?","acceptedAnswer":{"@type":"Answer","text":"Dual writes push every update to both the legacy and new system from the application layer, which is simple to build but fails under load since a partial failure leaves one system ahead with no record of which is correct. Change data capture instead reads the legacy database's write-ahead log and replays changes asynchronously, decoupling the write path and typically introducing under a second of replication lag when properly tuned, versus minutes-long lag for polling-based approaches. Weighing dual writes against CDC for a live migration is exactly the kind of tradeoff daily.dev helps engineers research."}},{"@type":"Question","name":"Which capability should you strangle first when applying the strangler fig pattern?","acceptedAnswer":{"@type":"Answer","text":"Start with a capability that has the fewest upstream dependencies, a narrow write surface, is read-heavy, and sits behind an interface the facade can intercept without touching shared mutable state. Avoid picking the biggest, most painful module first, since it's usually wired into shared tables, batch jobs, and fields that other services depend on, forcing the hardest reconciliation work before the team has run the pattern once. Sequencing a monolith decomposition is easier when developers can pull in real architecture experience via daily.dev."}},{"@type":"Question","name":"Why do strangler fig migrations often stall before reaching completion?","acceptedAnswer":{"@type":"Answer","text":"Strangler migrations commonly stall around 80% done because the remaining slices are the ones nobody scoped upfront, such as batch jobs with undocumented side effects or reporting pipelines nobody owns, while the business has already banked the win from the flagship capability going live. The fix is funding migrations through decision gates tied to legacy retirement rather than to feature parity on the new system. Tracking why modernization projects stall helps teams planning a migration on daily.dev avoid the same trap."}}]}
```

