Our six-month routing shim just turned two. Do we bless it or kill it?

24 months ago we put a 200-line routing shim in front of the monolith. Plan was 6 months. Route slices to new services, retire the monolith, delete the shim.

Migration stalled with 70% of traffic still going through the shim. It absorbed auth checks and rate limiting along the way. No team owns it on paper. Vendor contract just got renewed for 12 more months.

Do we bless the shim as permanent and fund it properly? Or set a kill date and force the migration through?

Unowned box terminating auth is a breach with a date. Blessing changes nothing. Who patches Friday’s CVE?

Blessing changes nothing.

70% still on the shim means this stopped being temporary last year. Sam is right, a blessing without an owner fixes nothing. I do not run tech, I sign budgets, and unowned boxes always land in the same gap.

Our last orphan box got 25% of a borrowed engineer, never on paper. It worked until it didn’t.

Reminded me of a line I read: “It is what happens when a prompt becomes a shared dependency without becoming a shared API.” Alex’s shim is the same shape, every team routes through it with no owner and no contract.

12 more months of renewal buys time, not ownership. Who here would actually sign for that headcount?