Integration of API management details (Part 4)

Integration of API management details (Part 4)

In Part 3 of this series, we started diving into the details that determine how your integration becomes the key to transforming your customer experience.

It started with laying out the process of how I’ve approached the use case by researching successful customer portfolio solutions as the basis for a generic architectural blueprint. Now it’s time to cover various blueprint details.

This article takes you deeper into specific elements (API management and reverse proxy) of the generic architectural overview.

Architectural details

As mentioned before, the architectural details covered here are based on real customer integration solutions using open source technologies. The elements presented here are then the generic common architectural elements that I’ve identified and collected in a generic architectural blueprint. It’s my intent to provide a blueprint that provides guidance and not deep technical details.

Generic common architectural elements

This section covers the visual representations as presented, but it’s expected that they’ll be evolving visually over time. There are many ways to represent each element in this architectural blueprint, but I’ve chosen icons, text, and colors that I hope are going to make it all easy to absorb. Feel free to post comments at the bottom of this post, or contact me directly with your feedback.

Now let’s take a look at the details in this architecture and outline the elements uncovered in my research.

Everything you need to grow your career.

With your free Red Hat Developer program membership, unlock our library of cheat sheets and ebooks on next-generation application development.

SIGN UP

API management

Gateways into an organization are split between managing API access and hiding the actual landscape behind accessing services in the organization. The first element I identified was a management platform for handling API gateway activities.

Management platform for handling API gateway activities

API management refers to how access is provided to an organization’s services. It’s the critical path for access internally to services as well as externally.

Researching customer portfolio solutions revealed that API management provides access to service interfaces, applications, and other integration microservices. It’s providing scalability, reliability, and interface usage metrics that customers evaluate during operations monitoring.

In the generic architecture blueprint, it’s managing interfaces from the following:

  • Front-end microservices (providing access to internal integration microservices)
  • Process facade microservices (providing access to automated integration processes)
  • Other applications (providing access to aggregated microservices or other internal applications)

Part of the process of eventual access from external parties to internal services through interfaces involves hiding the specific networking details. To do this, we’ll examine reverse proxies details.

Reverse proxies

This covers various solutions found in research, but all are delivering the same functionality.

Reverse proxies

The basic security is achieved through these proxies, because they are acting on requests from third parties. By retrieving requested resources for their clients, all external parties are prevented from having actual access to internal networks.

Interactions on behalf of their clients provide them access to the following microservices:

  • Front-end microservices (providing access to internal integration microservices)
  • Process facade microservices (providing access to automated integration processes)
  • Other applications (providing access to aggregated microservices or other internal applications)

These details are not all-telling, but should give you the guidance you need to get started in your own architectural situations.

What’s next

This overview covers the API and proxy elements that make up our architecture blueprint for the omnichannel customer experience use case.

An overview of the series on omnichannel customer experience portfolio architecture blueprint can be found here:

Catch up on any articles you missed by following one of the links above.

Next in this series, taking a look at the details of specific elements in an architecture for omnichannel customer experience.

To learn more, visit our Linux containers or microservices pages.

Join Red Hat Developer and get access to handy cheat sheets, free books, and product downloads that can help you with your microservices and container application development.

Join Red Hat Developer and get access to handy cheat sheets, free books, and product downloads.

 

Do you need DevOps training and tutorials?

Visit our DevOps Topic page.

Join the Red Hat Developer Program (it’s free) and get access to related cheat sheets, books, and product downloads that can help you with your DevOps efforts.

For more information about Red Hat OpenShift and other related topics, visit: OpenShift, OpenShift Online.

Share