Jun 202013

The API Economy has exploded. The use of APIs today is so prolific that the number of publicly-exposed APIs has grown exponentially to the tens of thousands, and is expected to increase even further as non Internet-centric companies are starting to realize its business potential. We’re finding that as businesses begin to expose and combine their information resources with those of others to build new and innovative assets, a whole new market of customers becomes available — creating a new channel for businesses to generate revenue and gain a competitive edge.

Sounds like a win-win situation — but is it too good to be true? What are the risks of exposing your data assets and technologies to the world via APIs? How can exposed APIs be effectively combined to create innovative and profitable solutions for all parties involved?

An upcoming issue of Cutter IT Journal, with Guest Editors Giancarlo Succi and Tadas Remencius, addresses the API Economy and invites practical advice and guidance on how APIs can be used to increase the value of your information assets, enhance business agility, and drive organizational growth. We also seek insight on the possible challenges and risks of the API Economy, and specific practices that can ensure your APIs are being properly managed, delivered and secured.

Topics may include, but are not limited to the following:

* What are the benefits and pitfalls in exposing your technology through APIs?
* How can organizations effectively benefit from available APIs exposed by other parties?
* What technological issues must be considered for successful API exposure/usage?
* How can API exposure/usage lead to better ROI, market competitiveness and agility, and long term sustainability?
* What are the risks of having external developers use your newly exposed APIs? How can these risks be managed?
* What are the risks of using APIs exposed by other parties? How can these risks be mitigated?
* How can you revise your current agile processes to compete effectively in the API economy?
* How will the role/dynamics of the IT department be affected by the exposure/usage of APIs?
* What is the role of crowdsourcing in API implementation/usage?
* What kind of security measures should be taken to ensure the development/usage of secure APIs?
* What cultural/organizational challenges must be overcome for successful API exposure/usage?
* How can APIs be used to enhance your current IT applications?
* In which business scenarios have you found APIs to be most helpful?
* What lessons have you learned, and/or best practices would you share?

DEADLINE EXTENDED: Please send us your article idea asap for consideration — issue publication date September/October.

Please respond to the Guest Editor Giancarlo Succi, gsucci[at]cutter[dot]com with a copy to Christine Generali, cgenerali[at]cutter[dot]com and include an extended abstract and a short article outline showing major discussion points.

Editorial Guidelines


 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>