In our company, this is 90% responsible for the paralysis that is keeping us from migrating from a 10 year old enterprise architecture. It is designed in such a way that makes it hard for us to extend and scale, but the whole foundation of our business rests on this outdated model. It's to the point that the only way we can move forward is to start over.
I've read about technical debt, but it's usually in reference to code design, lack of proper testing, and tightly coupled dependencies.
And we definitely suffer from "infrastructure debt" as this article describes, but I feel this is the least of our problems.
To me, possibly the most expensive kind of debt to be in is database design debt, as everything rests on this. At least this is the case where I work.