Frameworx Home

Application Framework (TAM)

Business Process Framework (eTOM)

Business Process Framework Flows

Information Framework (SID)

Business Metrics High Level

All Diagrams

Frameworx Processes

Frameworx Applications

Information Framework ABEs

Frameworx Metrics

Views

Frameworx Application: API Management

Category: (1) TAM Application Type

Application Identifier: 10.3

Maturity Level: 4

Overview

API Management solutions offer different typologies, depending on many factors such as expertise, strategy, budget, etc. The following components are generally recognized as the set of applications that cooperatively address API Management requirements:

  • “API Broker”, “API Gateway” or simply, “API Runtime”

§  High-performance, scalable, and low latency engine capable of mediating HTTP requests between APIconsumers and service enablers;

§  Mediation of high throughput of HTTP requests between API consumers and services;

§  Awareness and support of Web protocols semantics (MIME types, HTTP Authorization and Caching headers, etc.);

§  Support of Data Format, Data Model transformations and Protocol Bridging between most or all common Web standards (WS-*, SOAP, XML, REST, JSON, etc.);

§  Content-based routing, fail-over, load balancing, and broadcasting of requests;

§  Support of standard authentication and authorization protocols (WS-Federation, SAML, OAuth, etc.), for both internal and external applications, API developers and users;

 

  • API Lifecycle Management application

§  Supports the processes required for designing, developing, testing, deploying, operating, reporting and retiring APIs;

§  API Catalog Management: a common database containing metadata related to: API creation driven by project definition templates and configuration wizards, API dependencies registry, API search, API contracts management, API proxies and stubs code-generators, etc.;

§  Access control policies based on a Role-Based Access Control (RBAC) system that restrict permissions for APIs creation and delivery, thus enabling different stakeholders experiences (for example: Catalog Manager, Service Developer, Service Operator, Service Owner, Product Manager, etc.);

§  Configuration of all API Runtime behaviors (see previous component) using a model-driven language or other type of DSL (Domain-Specific Language);

§  Real-time monitor and report QoS (requests per second, exceptions, latency, etc.);

 

  • Developers Portal

§  Technical/commercial API Catalogue;

§  Easy to search and discover APIs;

§  API documentation and code examples;

§  Performance and usage reports;

§  Technical support (online, email, forums, etc.).

 

Functionality

Supported Business Services

(1) TAM Application Type API Management

Appears on these diagrams:

Issues

  • Application Framework 13.0 Addition

Frameworx Domains (Horizontal)


This was created from the Frameworx 16.0 Model


Created from the TM Forum Model Frameworx 16.0.0 on 6/13/2016 at 22:30