Understand the Power of Internal APIs
One of the biggest mistakes in modern information technology is using the wrong tool for the job. Any software architect will tell you that each layer has an area of responsibility. Though you could hack together a way to force more functionality where it doesn’t belong, it almost never turns out well. Usually, it just leads to maintenance costs, flaky integrations, the burden of supporting a proprietary architecture, and so on.
This is an escalating challenge because businesses expect more from their technology groups than in the past. IT is no longer just the curator of infrastructure; increasingly, it’s the enabler of new business opportunities and efficiencies. Now, more than ever, it’s important to use the correct tools and to identify solutions for today’s problems.
Most enterprise leaders understand this urgency, but in trying to address it, many make a big mistake: they think an API (application programming interface) platform is only for external use cases. For internal use cases, they turn to integration point solutions in which APIs are only designed within the narrow scope of the integration project at hand, not to facilitate developer consumption or support future extensibility.
Due to this mistake, many businesses limit the potential of one of the most powerful tools in the internal IT arsenal, cost themselves time and money, and risk disappointing their users.
Continue reading this story in InformationWeek.