organizations to elastic storage, cloud scale data analytics and packaged
ML to store all the data, analyze the information, and surface meaningful
signals. Traditional infrastructure approaches and data storage will simply
not scale.
API mediation and architecture
The top 3 recommendations for API mediation and architecture include:
1. Mediate APIs to improve observability and monitoring capabilities
2. Use mediation mechanisms like API gateways to enforce access control
3. Augment your mediation mechanisms with API security tooling that can provide
context
While it’s possible to directly expose an API
via a web or application server, this
practice is less common in typical
enterprise architectures. API mediation can
be achieved through a number of other
mechanisms as well, including network
load balancers, application delivery
controllers, Kubernetes ingress controllers,
sidecar proxies, and service mesh
ingresses. Design patterns like API facade
and front-end for back-ends involve
putting a proxying mediation layer “in front
of” APIs. Typically, this design pattern is
achieved by deploying API gateways that
function as reverse proxies, forward
proxies, or both. API management suites
and integration platforms also make use of
API gateways to enable their functionality and enforce policies. Mediation provides
a wide range of benefits including improved visibility, accelerated delivery,
increased operational flexibility, and improved enforcement capabilities, particularly
when it comes to API access control.
Best practices for API mediation and architecture include:
1.
Dostları ilə paylaş: