<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ziad hatem</title>
    <description>The latest articles on DEV Community by ziad hatem (@ziad_hatem).</description>
    <link>https://dev.to/ziad_hatem</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2327335%2F41432146-18b7-4309-bb67-9452d42637a1.png</url>
      <title>DEV Community: ziad hatem</title>
      <link>https://dev.to/ziad_hatem</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ziad_hatem"/>
    <language>en</language>
    <item>
      <title>How to Migrate a Legacy System Without Breaking Production</title>
      <dc:creator>ziad hatem</dc:creator>
      <pubDate>Wed, 22 Apr 2026 22:58:18 +0000</pubDate>
      <link>https://dev.to/ziad_hatem/how-to-migrate-a-legacy-system-without-breaking-production-4dim</link>
      <guid>https://dev.to/ziad_hatem/how-to-migrate-a-legacy-system-without-breaking-production-4dim</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/google-cloud-next-2026-04-22"&gt;Google Cloud NEXT Writing Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;How do you change an entire production system… without a single minute of downtime? 🤔&lt;/p&gt;

&lt;p&gt;There’s a common mistake many teams fall into:&lt;br&gt;
“Let’s throw away the old system and rewrite everything from scratch.”&lt;br&gt;
That’s the classic Big Bang Rewrite.&lt;/p&gt;

&lt;p&gt;And the usual result?&lt;/p&gt;

&lt;p&gt;🔥 Delays&lt;br&gt;
🔥 Bugs&lt;br&gt;
🔥 Production issues&lt;br&gt;
🔥 And in the end… crawling back to the old system 😅&lt;/p&gt;

&lt;p&gt;💡 The smarter approach: Strangler Fig Pattern&lt;/p&gt;

&lt;p&gt;The idea is simple:&lt;br&gt;
Instead of killing the old system all at once…&lt;br&gt;
you slowly “strangle” it until it disappears completely 👀&lt;/p&gt;

&lt;p&gt;🧠 How does it work?&lt;/p&gt;

&lt;p&gt;1- Keep the legacy system running as usual&lt;br&gt;
2- Start building new parts feature by feature&lt;br&gt;
3- Put a proxy / routing layer in front of the system&lt;br&gt;
4- Route some requests to the new system&lt;br&gt;
5- Keep the rest going to the old one&lt;br&gt;
6- Repeat until the legacy system is fully gone&lt;/p&gt;

&lt;p&gt;🎯 Practical example:&lt;/p&gt;

&lt;p&gt;/products → still handled by Legacy Laravel&lt;br&gt;
/checkout → handled by Next.js (the new system)&lt;/p&gt;

&lt;p&gt;The proxy is what decides where each request goes.&lt;/p&gt;

&lt;p&gt;👍 Why is this smarter?&lt;/p&gt;

&lt;p&gt;Lower risk&lt;br&gt;
You can deploy while still developing&lt;br&gt;
Rollback is easier&lt;br&gt;
The team keeps moving without stopping the business&lt;/p&gt;

&lt;p&gt;⚠️ But here’s the catch:&lt;/p&gt;

&lt;p&gt;If you don’t have discipline,&lt;br&gt;
you may end up with:&lt;/p&gt;

&lt;p&gt;❌ A broken old system&lt;br&gt;
❌ And a new system that still isn’t ready&lt;/p&gt;

&lt;p&gt;= a double disaster 😅&lt;/p&gt;

&lt;p&gt;🧨 The most important rule:&lt;/p&gt;

&lt;p&gt;Every migrated part must be:&lt;/p&gt;

&lt;p&gt;✔️ Isolated&lt;br&gt;
✔️ Clear&lt;br&gt;
✔️ Owned by someone&lt;/p&gt;

&lt;p&gt;And most importantly:&lt;br&gt;
👉 Kill the old system fast. Don’t let it live forever.&lt;/p&gt;

&lt;p&gt;🧭 Final takeaway:&lt;/p&gt;

&lt;p&gt;Strangler Fig Pattern = migrating a legacy system gradually using a routing layer until the old system is fully replaced.&lt;/p&gt;

&lt;p&gt;If you’re working with a monolith and thinking about moving to microservices — or even just rewriting your frontend — this is often the smartest strategic move you can make.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>cloudnextchallenge</category>
      <category>googlecloud</category>
    </item>
  </channel>
</rss>
