Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

Strangler not big-bang

This revision card explains Strangler not big-bang. It starts from the need that weekend rewrites of monoliths burn teams and customers. It describes route new slices to Lambda behind a facade; leave the rest on the monolith. The how-to section notes pick one capability , then parity tests , then route % traffic , then keep rollback. An example on the card is priya Deshmukh migrates read APIs first, writes later.

Strangler not big-bang Weekend rewrites of monoliths burn teams and customers. Route new slices to Lambda behind a facade; leave the rest on the monolith. Pick one capability → parity tests → route % traffic → keep rollback. Priya Deshmukh migrates read APIs first, writes later.
Strangler not big-bang · Download PNG
Read card text

What this card says

Why do we need it?

Weekend rewrites of monoliths burn teams and customers.

What is it?

Route new slices to Lambda behind a facade; leave the rest on the monolith.

strangler fig

How to do it

Pick one capability → parity tests → route % traffic → keep rollback.

Example

Priya Deshmukh migrates read APIs first, writes later.

See all AWS revision cards