4 ms·
4. A couple of years later you want to stop an obsolete interface but you can't because a handful of systems use it and they dont have budget to change.
by rb808 7y ago
4. A couple of years later you want to stop an obsolete interface but you can't because a handful of systems use it and they dont have budget to change.
- jrd259 7y agoTrue this happens, but you're still better off that if you had tight coupling. In the absolute worst case you can make a shim implementation to support the obsolete use case. You can not do this when callers are directly reading your database/memory structure.
- wil421 7y agoYep, I’ve implemented new ticketing systems that have to talk to the ancient ticket system for certain things or vice versa. The ancient system had direct DB connections that had too many down/upstream dependencies and not enough budget or political backing.