• Welcome And Introduction
    • About
    • FAQ
    • Coverage
    • Services
    • Ethics Statement
  • Tom Petrocelli
    • Contact
    • Animated Tom Petrocelli
  • Social Media Analytics Explained

Tom's Tech Take II

Tom Petrocelli's Musings on Tech

As API Management Problem Grows, Informatica Jumps into the Market

January 2, 2018 by Tom Petrocelli

This originally appeared on the Amalgam Insights website on January 2, 2018

API management is a necessary but boring practice. As developers make use of a mix of public cloud, purchased or open source libraries, and homegrown services, the number of APIs used by developers quickly renders pouring through documentation impractical.

Microservices, usually accessed via RESTFul APIs, cause API calls to rapidly proliferate. Even modest sized microservices-based systems experience API overload quickly. Agile development can exacerbate the problem of understanding and using APIs. The rapid pace of Agile, especially Scrum, leaves little time for proper documentation of APIs. Documentation often takes a back seat to continuous deployment.

There are a number of other concerns with API management aside from simply documenting APIs. Once APIs are in widespread use, they need to be actively managed to ensure that they haven’t changed and are only accessed securely. Access control of APIs becomes especially important when these are exposed to customer, partners, and the developer community, and monitoring of API performance.

For a developer to use an API properly they must understand the following:

  • which API calls exist
  • how the API are used and function
  • what parameters are available and what data structures the API call expects
  • is access to API calls restricted and what controls exist on that access
  • how the API calls are authenticated
  • error conditions and error codes
  • what the expected result sets and data structures are

That’s a lot to remember. Good documentation and reference books exist for major open source and commercial services but not for homegrown and lesser known APIs.

At the heart of API management is a data problem, more accurately a data management problem. The APIs themselves are a form of data – information that tells a developer how to access a service – and the documentation and controls the metadata. Managing APIs, which are sources of services, is not much different than cataloging, exposing, monitoring, and otherwise managing data sources.

It’s not that surprising then that Informatica has entered the API management market, alongside IBM, Microsoft, MuleSoft, and a host of others. Finding, managing, and securing data sources are Informatica’s bread and butter competency. With developers already using their software to manage data sources, it’s natural for those same customers to want Informatica to help them manage the APIs for the services they create to access and manipulate that data.

As microservices architectures become more prevalent and companies need to expose APIs both internally and to their partners and customers, the need for API management will only grow. Sure, it’s dull but so is changing the oil in your car. It’s not good practice to ignore either.

Posted in: developers, DevOps, IBM, Informatica, Microsoft, service, software trends, Software vendors Tagged: API management

Pages

  • Tom Petrocelli
    • Contact
  • Welcome And Introduction
    • About
    • Coverage
    • Ethics Statement
    • FAQ
    • Services

Recent Posts

  • Firefox and Microsoft Acting Weird… or Is It?
  • Yep, This Looks Different
  • Hey Microsoft, Are You Watching for Bad Tech Advice?
  • Slicing GitOps Baloney Thin
  • Why I like Mastodon Better Than Twitter

Archives

  • May 2023
  • February 2023
  • December 2022
  • November 2022
  • January 2021
  • December 2020
  • September 2020
  • July 2020
  • May 2020
  • April 2020
  • March 2020
  • January 2020
  • November 2019
  • September 2019
  • August 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • April 2017
  • September 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013

Categories

  • Amazon
  • analytics
  • animation
  • big data
  • Change
  • cloud
  • cognitive computing
  • collaboration
  • conference
  • CRM
  • customer experience
  • developers
  • DevOps
  • digital culture
  • email
  • engagement
  • Google
  • HP
  • IBM
  • IBM
  • infographic
  • Informatica
  • intellectual property
  • IoT
  • IT Buy
  • Linux
  • marketing
  • Microsoft
  • mobile
  • Netsuite
  • Oracle
  • Red Hat
  • Salesforce.com
  • SAP
  • security
  • service
  • skills
  • social
  • social enterprise
  • social media
  • software trends
  • Software vendors
  • Support
  • This Site
  • Tom Petrocelli
  • Tomfoolery
  • Ubuntu
  • Uncategorized
  • video
  • VMware

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Copyright © 2023 Tom's Tech Take II.

Omega WordPress Theme by ThemeHall