Discover how you can get APIs and microservices to work at true enterprise scale.

As part of any API management platform rollout project, a new API publication pattern targeting API consumers should be promoted: experience-based APIs.

This approach will become the driver for self-service API management, enabling consumer-specific API wrappers that are designed and implemented by the consuming teams.

This article provides an overview of the pattern, emphasizing the benefits and value created by its adoption.

Façade APIs Sit Between Consumer and Legacy APIs

Façades and proxies are a well-known pattern of integration architects with traditional EAI and SOA knowledge. They bring multiple benefits and offer a wide set of capabilities that can enrich the functionality offered by the legacy APIs being proxied.

The Proxy pattern can be extended to enable the creation of multiple Proxy endpoints, each one dedicated to a specific API consumer.

These new Proxy endpoints will be designed, developed, and configured focusing exclusively on the business requirements of their API consumers. Proxy capabilities (transformation, protocol bridging, etc.) can be applied per endpoint, leading to the availability of tailored proxy endpoints that can expose functionality somewhat disparate than the original legacy API.

It is also a good practice to make available a generic one-size-fits-all proxy endpointto support consumers that need no tailoring of the legacy API business function. Organizations have been successfully exposing and consuming these generic endpoints for a long time, and their immediate decommissioning would not make sense.

There are three key principles that must not be disregarded when implementing the Experience based APIs pattern. Their aim is to ensure maximum value can be derived from the pattern adoption.

It is important to understand the consumers of an API. Only then can a decision be made if experience and/or general-purpose endpoints are required.

Most APIs are designed by providers and focus on data model purity. Experience-based APIs target optimizations and/or performance — not the data model.

Many APIs are designed by API teams with facilitated support in mind. The exposure of experience-based APIs can bring extra complexity to the support processes.

General purpose APIs are currently exposed, providing reusable functionality to multiple user-facing applications. However, desktop, mobile, wearables, and other devices’ experiences differ drastically. The functionality exposed is also different.

Self-service is crucial to the pattern since it empowers API consumers to design, implement, and configure their own API proxy endpoints. API consumers will have full control and ownership of the proxy endpoints they consume.

Predicted Benefits

Contribute to a smoother customer journey and exceptional customer engagement. Support a mobile first strategy, delivering APIs that: