· 9 min read
Two Code Paths During a Strangler Migration
Incremental replacement behind an existing system means two implementations coexist for the whole migration, with a routing seam between them. That is a real cost rather than a detail. Routing rules, shared state, sessions that cross the boundary and the criteria for declaring a path finished all have to be designed up front, because the alternative is discovering the seam's behaviour from incidents.