Book Image

Enterprise API Management

By : Luis Weir
Book Image

Enterprise API Management

By: Luis Weir

Overview of this book

APIs are the cornerstone of modern, agile enterprise systems. They enable access to enterprise services from a wide variety of devices, act as a platform for innovation, and open completely new revenue streams. Enterprise API Management shows how to define the right architecture, implement the right patterns, and define the right organization model for business-driven APIs. Drawing on his experience of developing API and microservice strategies for some of the world's largest companies, Luis Weir explains how APIs deliver value across an enterprise. The book explores the architectural decisions, implementation patterns, and management practices for successful enterprise APIs, as well as providing clear, actionable advice on choosing and executing the right API strategy in your enterprise. With a relentless focus on creating business value, Luis Weir reveals an effective method for planning, building, and running business products and services with APIs.

Related Content you might be interested in

Current Title:

Small book image
Enterprise API Management
Luis Weir
Jul, 2019 | 300 pages
Small book image
Implementing Oracle API Platform Cloud Service
Sander Rensen | Andrew Bell | Phil Wilkins | Luis Weir
May, 2018 | 518 pages
Small book image
Designing API-First Enterprise Architectures on Azure
Subhajit Chatterjee
Aug, 2021 | 290 pages
Small book image
Building an API Product
Bruno Pedro
Jan, 2024 | 278 pages
Table of Contents (9 chapters)
Preface
Preface
Who this book is for
What this book covers
Get in touch
Free Chapter
1
The Business Value of APIs
The Business Value of APIs
Change or die
What are APIs and why should a business care?
Avoiding a hyperconnectivity mess
The API value chain
APIs as a driving force for many large acquisitions in the software industry
Summary
2
The Evolution of API Platforms
The Evolution of API Platforms
The journey of API platforms - from proxies to microgateways
Summary
3
Business-Led API Strategy
Business-Led API Strategy
Kick-starting a business-led API initiative
Summary
4
API-Led Architectures
API-Led Architectures
What is API-led?
Architecting API-led
Summary
5
API-Led Architecture Patterns
API-Led Architecture Patterns
Patterns in the context of APIs
API-led architecture patterns described
Summary
6
Modern API Architectural Styles
Modern API Architectural Styles
A brief history of interfaces
REST
GraphQL
gRPC
Comparing the options
Summary
7
API Life Cycle
API Life Cycle
The full API development life cycle
Summary
8
API Products' Target Operating Model
API Products' Target Operating Model
Products in the real world
APIs as products
What is a TOM?
Defining the model
Organization
Roles and responsibilities
Communication and collaboration model
Transition approach
Summary

GraphQL

The Graph Query Language (GraphQL) was created by Facebook around 2012 by engineers Lee Byron, Dan Schafer, and Nick Schrock. It was open-sourced three years later, in 2015.

Figure 6.10: The GraphQL logo
The GraphQL project is accessible through its official website:
https://graphql.org/

As described by Byron himself in one of his articles, GraphQL came at a time when Facebook's iOS and Android mobile apps were just thin wrappers (mobile WebView) of Facebook's web application. As the number of users grew, so did the complexity of the mobile WebView and thus it started suffering from poor performance and it constantly crashed.

To overcome this challenge, Facebook started transitioning its apps into natively implemented views (as opposed to just web wrappers). However, this raised the need for a mechanism other than HTML to fetch data. In other words, there...

Previous Section
End of Section 4
Next Section