INTERMEDIATE · 8 MODULES · 64 LESSONS

Legacy Modernization and Migration

Modernize a legacy system without rewriting it from scratch: protect it with tests, migrate piece by piece without stopping the business, and measure when the migration is really done.

For you if
You inherited a monolith with no tests that's scary to touch, and the business can't stop.
By the end
You'll know how to apply strangler fig and branch by abstraction, extract a service, and migrate data with zero downtime.
You need
Experience with backend services in production, basic unit testing, and Python for the simulations.
  1. 01Por qué no reescribir8 LESSONS
    1. Module introduction: why not rewrite
    2. Why the big rewrite fails
    3. The second-system syndrome
    4. The tacit knowledge buried in the legacy
    5. The case for incremental
    6. The strangler fig metaphor
    7. Modernize in place vs start from scratch
    8. Mini-project: build the defense against Mercado's rewrite
  2. 02Entender y fijar el legacy8 LESSONS
    1. Module introduction: understand and pin the legacy
    2. Working with code that scares you and has no tests
    3. The characterization test: pin what it does TODAY
    4. Finding the seam
    5. Characterizing by sampling and the golden master
    6. When the legacy does something weird (and someone depends on it)
    7. Read and characterize before you change
    8. Mini-project: pin Mercado's catalog pricing
  3. 03El patrón strangler fig8 LESSONS
    1. Module introduction: the strangler fig pattern
    2. The facade in front of the legacy
    3. Building the new service alongside
    4. Diverting traffic by percentage
    5. Ways of diverting: by route, by percentage, by flag
    6. Fallback and observing both routes
    7. The final cutover and retiring the legacy
    8. Project: put Mercado's catalog behind a strangler facade
  4. 04Branch by abstraction8 LESSONS
    1. Module introduction: branch by abstraction
    2. The abstraction layer as a seam
    3. Building the modern implementation behind the abstraction
    4. The feature flag as the switch point
    5. Parallel-run to prove the swap is safe
    6. Deleting the old implementation
    7. Without a long-lived branch: avoiding merge hell
    8. Project: modernize Mercado's ShippingCalculator
  5. 05Extraer un servicio8 LESSONS
    1. Module introduction: extracting a service
    2. Finding the bounded context
    3. The anti-corruption layer
    4. Translating in both directions
    5. Owning the data
    6. Cutting the shared DB
    7. The order of extraction
    8. Project: extract Mercado's catalog into a service
  6. 06Migrar datos sin downtime8 LESSONS
    1. Module introduction: migrating data without downtime
    2. Expand-contract: never a destructive change all at once
    3. Dual-write: writing to both stores
    4. Backfill: loading the historical data
    5. Parallel-run: comparing both stores
    6. Reconciling the discrepancies
    7. The read-switch and turning off the dual-write
    8. Project: migrate Mercado's catalog data without downtime
  7. 07Medir el progreso de la migración8 LESSONS
    1. Module introduction: measuring the migration's progress
    2. Measure the result, not the effort
    3. The legacy-call burn-down
    4. The migration fitness function
    5. Keeping the legacy from growing back
    6. Defining "done": when the legacy gets deleted
    7. Avoiding the eternal migration
    8. Project: measure and finish the Mercado migration
  8. 08Proyecto — modernizar una rebanada de Mercado8 LESSONS
    1. Capstone introduction: seven techniques, one method
    2. Choose and characterize the slice
    3. Put the slice behind the facade
    4. Extract the service with an anti-corruption layer
    5. Migrate the slice's data
    6. Measure the slice's progress
    7. Declare done and retire the legacy
    8. Project: modernize Mercado's catalog
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab