API governance is an architecture problem, not a developer problem
When API proliferation becomes an architectural liability, the solution is never more developer tooling. It is governance decisions that should have been made earlier.

When API proliferation becomes an architectural liability, the solution is never more developer tooling. It is governance decisions that should have been made earlier.

Enterprise architecture programmes organised around projects rather than platforms consistently produce the same outcome: capability delivered, capability degraded, capability rebuilt.

I have sat through a lot of build vs buy debates. They follow a predictable pattern. Someone presents a shortlist of vendors. Someone else argues the vendors cannot do what is needed. A third person suggests building it in-house. The debate becomes about capability and cost without ever establishing what the decision is actually for….

A reference architecture document that lives in a SharePoint folder nobody visits is not an architecture asset. It is a monument to good intentions. The value of reference architecture is determined entirely by how easily it can be found and used at the moment a decision is being made.