A client once asked me to add full multi-tenancy and audit logging to a live SaaS — without touching a single one of its 132 existing tables.
No downtime. No migrations on the old schema. Real users on it the whole time.
The solution wasn't clever code. It was restraint: new tables only, tenant scoping layered on top, audit trail bolted to the side, existing logic untouched.
Good architecture is usually less about what you build and more about what you refuse to break.
What's the gnarliest "don't break the existing system" constraint you've ever had to work under?