This is part 2 of my API blog series. In my previous blog, we talked about the basics of APIs. In this blog, we’ll look at API Management.

Every enterprise from small to large would have API’s created initially to connect and integrate between the existing systems so that those systems can seamlessly transact data between each other. Before we eventually expose API’s as business services externally (as a solution) the primary need would be to have internal integrations successfully accomplished with those API’s.

API Management done wrong

If an enterprise is going to have API’s, the underlying integration pattern without API management would look like the image below. The representation depicts the user experience layer or the exposed applications having multiple integration points to the technology assets of the enterprise without having streamlined API management which results in reduced performance, less reusability, increased time to market, the return of investment is a question and value creation is meager.

User Experience Layer

Introduction to API Management 1

Technology Assets / Systems Layer


API Management done right

The image below represents an enterprise with well-defined API Management

User Experience Layer

API management done right

Technology Assets / Systems Layer

This enterprise structure is well organized because they have all technology assets grouped as System API’s, this means there will be connectors – reusable APIs to the systems of the organization. Process layer is where all the core business operations of the organization will reside and only the process layer API’s are responsible to communicate with the System level through connector API’s.

Experience level delivers high performance driven and efficient API’s where end users would be happy utilizing it as a service.

An idealistic view of an API Manager Architecture has the following characteristics:

  • System API’s -> Unlock the legacy assets and decentralize access.
  • Process API’s -> Delivers agility and new value creation.
  • Experience API’s -> Opens up the path for Innovation and happy customer base.


API Manager Architecture

API Manager Architecture

API Management Architecture as a core to make the API’s effectively managed across the enterprise for better business, integrations and operational results.

The portal is a central console to visualize API’s performance, revenue results, predictions, documentations, registries and analytics etc…

The gateway is where the proxying of the actual API backend happens, these gateway services are the ones exposed to the external partners. Gateway services are enabled with a high level of security and governance protocols. Internal integrations are with enterprise applications, mobile applications, and partners of API’s.

In a nutshell, once we have rightly implemented API management in an enterprise, it would result in

  • A better-managed developer community
  • Good control over API traffic
  • Uncover potential monetization API’s
  • A gradual increase in performance of API’s
  • Robust security and governance process


Learn more about API Management



Please enter your comment!
Please enter your name here