Ravi Sir's Cards › AWS
Behavioral parity
This revision card explains Behavioral parity. It starts from the need that shipping a different response shape breaks every client silently. It describes compare status, body, and side effects old vs new before cutover. The how-to section notes shadow traffic , then diff logs , then then serve Lambda responses. An example on the card is kenji Tanaka keeps a one-click route rollback for a week.
Read card text
What this card says
Why do we need it?
Shipping a different response shape breaks every client silently.
What is it?
Compare status, body, and side effects old vs new before cutover.
parity
How to do it
Shadow traffic → diff logs → then serve Lambda responses.
Example
Kenji Tanaka keeps a one-click route rollback for a week.