API Management Vs API Gateway
API Management Vs API Gateway
For the last few years, there has been an explosion of API powered businesses. There are
revenue generating APIs, developer platforms, partner marketplaces, and even internal APIs
powering single page apps.
With this explosion, there has also been a large increase in API tooling to help these
companies go to market with their API platforms as quick as possible and out innovate any
competition. Much of this increase in tooling mirrors what we saw in the mobile era.
However, with this explosion, there is now an increase in number tools and solutions to build
and grow APIs and platforms.
In addition, tools like API gateways can be used both as a proxy in front of public facing
APIs, but can also behave like a service mesh orchestrating between various internal services.
This guide aims to provide an overview of various API tools.
API GatewaysPermalink
An API Gateway is a HTTP server/proxy server that sits in front of your API and provides a
central place to administrate, route, and secure your APIs and services. API gateways should
be deployed in clusters so you can scale the system horizontally by adding more machines
and ensure high availability. API gateways are usually on-premises appliances, but modern
ones are usually based on an open-source or open-core model. For example, Kong is based on
NGINX and Express Gateway is based on Node.js Express.
There are also proprietary cloud-based solutions from cloud vendors like AWS API Gateway
and Azure API Management. Usually, an API gateway will do the following:
In addition to data transformation, some API gateways can also combine endto avoid API
chaining. This enables your customers to leverage a single public end point like GET
/user/me even though it has to fetch from various internal services like your authentication
service, user service, and billing service. The responses from those internal services are
combined into a single response to be returned to the client. This makes working with your
API easier for customers since they don’t have to perform API chaining. An extreme example
of this would be Apollo GraphQL which can fetch many entities from many services and
combine them into a single endpoint POST /graphql
While API management and API gateway solutions are designed for infrastructure and site
reliability engineering in mind, API analytics usually is designed with a broader audience of
both technical and non-technical users including product, engineering, and support. Because
of this, API analytics vendors like Moesif are more likely to be managed SaaS solutions
rather than on-premises, but can be homegrown also. Checkout our guide on when to build vs
buy an API analytics solution.
TTFHW measures how long it takes from first visit to your landing page to an MVP
integration that makes the first transaction through your API platform. This is a
cross-functional metric tracking marketing, documentation and tutorials, to the API
itself.
API Logging/DebuggingPermalink
Besides measuring product metrics like retention and engagement, API analytics also
provides an easy way to speed up investigating and debugging API functional and
performance API issues. High-cardinality log analysis enables you to plot trends using
heatmaps, time series, waterfall diagrams, and other charts. Some API analytics also log the
full API calls in real-time so you can inspect the request and response headers and body and
do a diff or even replay and generate tests from failing transactions.
API MonitoringPermalink
Many API analytics tools also provide API monitoring and alerting capabilities so you can
get notified when an API is down or acting incorrectly. Unlike synthetic monitoring which
are simple health probes, API Real User Monitoring , detects anomalous behavior from your
actual API traffic made by your customers based on historical trends. API issues could be
business related such as unexpected drop in API activity from key customers or it could be
engineering related such as functional or performance problems. Specifically, API analytics
focuses on a few key pillars:
Team DashboardsPermalink
Some API analytics solutions provide a way to share and collaborate on dashboards with both
technical and non-technical team members or automatically sandbox the usage data so you
can share dashboards directly to your external partners in a secure way. By embedding an
API debug log and plan usage information in your customer facing portal, customers can
resolve issues without overloading your already stretched support team.
API ManagementPermalink
While API Gateways and API management can be used interchangeably, strictly speaking an
API gateway refers to the individual proxy server, while API management refers to the
overall solution of managing APIs in production which includes a set of API gateways acting
in a cluster, an administrative UI, and may even include additional items such as a developer
portal for customers to sign up and generate new API keys.