By Dan Magid

The API economy is a new frontier for companies seeking to get the most out of their data. With the right API, you can transform rigid workflows into the intuitive web-based and mobile experiences that today’s users demand, using modern programming languages to access real-time transactional data. This way, users can harness the value of information from the transactional systems that fuel their businesses without unnecessary time, cost, and risk.

According to Coleman Parkes Research, 88% of all businesses employ APIs. But our internal research shows that only 38% of IBM i users are enjoying the benefits of the API economy. Perhaps this disparity is due to the lack of API expertise among IBM i shops, where most developers use RPG and COBOL vs. modern tools like Node.js or GO, or the time and resource constraints that are common among IBM i shops.

However, the fact is that APIs are the most effective way for IBM i shops to expose real-time transactional data for access by modern web, mobile and IoT applications, so bridging the knowledge gap between modern application development and the languages that power your critical IBM i applications should be a top priority. But it must be done without hurting productivity, blowing the IT budget or risking catastrophic application errors.

These goals—building and deploying APIs without negatively affecting organizational performance—may appear to be contradictory, but they don’t have to be. How do you do it? I recommend a two-pronged approach:

  • Look for tools to build APIs directly from the host-based application that run your business—but without needing to modify the codebase that runs your business
  • Ensure that your API functionality is easily tested against any other host-based application changes that occur, vastly reducing the resources required to ensure that APIs continue to work in a world of ever-changing user and IT requirements

Following this approach will enable you to not only extend the value of your IBM i platform, but also unlock the value of your applications to a world of new uses. And without the need to modify source code, it will also help you bridge the knowledge gap between your IBM i applications the web and mobile applications that need their functionality.

I’ll finish with the results of a recent study by Quark and Lepton, which showed that the IBM i platform typically costs about one-third as much budget to operate over a three-year period compared to Oracle/Linux or SQL Server/Windows platforms. IBM i is by far the most cost-effective, and with the right API approach, it can serve you effectively for years to come.

Guest Blogger

Daniel Magid is Managing Director of Rocket Software’s Application Lifecycle Management & DevOps lab, and is a recognized authority on helping leading organizations achieve compliance through ALM solutions and DevOps best practices. He has written a variety of articles for leading IT publications and is a regular speaker at technology conferences.

Leave a Reply

Your email address will not be published. Required fields are marked *