The Business of Creating Well-Defined APIs

APIs should be well-defined to minimize user frustration and maximize potential for use.

Traditionally, a software application would be designed in a silo to accomplish a specific function and might work within a custom architecture that bore little resemblance to the other application architectures with which it would be deployed. Bridging the gap between two application silos often required deep product knowledge, strong scripting skills and even a healthy dose of luck.

These days, application programming Interfaces (APIs) are used to simplify the process of integrating applications. Every day, billions of APIs are executed to run our businesses. But simply publishing APIs is not enough. APIs should be well defined, with clear guidelines for use, to minimize end user frustration and maximize potential for (re)use. To accomplish this, consistent API standards need to be part of the design process. Although this requires more up front work, it can make the development process smoother and position the application for future growth.

Sponsored by the Council for Technical Excellence (CTE).
 

By Stephen Breese and Yatin Dawada | June 30, 2016

Subscribe to The Blueprint

Share the wealth and suggest a friend to subscribe to The Blueprint:

At CA, your time and privacy are just as important to us as they are to you. We use the information you provide to us under our legitimate interests to make sure you hear about topics of interest to you. If we got it wrong you can update your preferences by clicking here. If you'd like to know more about how we use your personal information, you can read our privacy statement here.

Please fill out all required fields

You are now subscribed to The Blueprint.