ptlooki.blogg.se - Apptivate api

Monitoringįor details about monitoring options, see Observability in Azure API Management.

2 By default, rate limit counts in self-hosted gateways are per-gateway, per-node. Policyġ The rate limit by key and quota by key policies aren't available in the Consumption tier. Managed and self-hosted gateways support all available policies in policy definitions with the following exceptions. Backend APIs APIġ GraphQL subscriptions aren't supported in the Consumption tier.

2 Requires configuration of local CA certificates. See also self-hosted gateway limitations.ĬA root certificates for certificate validationġ Depends on how the gateway is deployed, but is the responsibility of the customer.Some features of managed and self-hosted gateways are supported only in certain service tiers or with certain deployment environments for self-hosted gateways.The self-hosted gateway is packaged as a Linux-based Docker container and is commonly deployed to Kubernetes, including to Azure Kubernetes Service and Azure Arc-enabled Kubernetes.Įach self-hosted gateway is associated with a Gateway resource in a cloud-based API Management instance from which it receives configuration updates and communicates status. The self-hosted gateway enables customers with hybrid IT infrastructure to manage APIs hosted on-premises and across clouds from a single API Management service in Azure. It's useful for hybrid and multicloud scenarios where there's a requirement to run the gateways off of Azure in the same environments where API backends are hosted. Self-hosted - The self-hosted gateway is an optional, containerized version of the default managed gateway. For details, see the section Feature comparison: Managed versus self-hosted gateways. With the managed gateway, all API traffic flows through Azure regardless of where backends implementing the APIs are hosted.īecause of differences in the underlying service architecture, the Consumption tier gateway currently lacks some capabilities of the dedicated gateway. Managed - The managed gateway is the default gateway component that is deployed in Azure for every API Management instance in every service tier. Emits logs, metrics, and traces for monitoring, reporting, and troubleshootingĪPI Management offers both managed and self-hosted gateways:.

If configured, caches responses to improve response latency and minimize the load on backend services.

Optionally transforms requests and responses as specified in policy statements.

Verifies API keys and other credentials such as JWT tokens and certificates presented with requests.

Acts as a facade to backend services by accepting API calls and routing them to appropriate backends.

The API Management gateway (also called data plane or runtime) is the service component that's responsible for proxying API requests, applying policies, and collecting telemetry. This article provides information about the roles and features of the API Management gateway component and compares the gateways you can deploy.įor an overview of API Management scenarios, components, and concepts, see What is Azure API Management?įor more information about the API Management service tiers and features, see Feature-based comparison of the Azure API Management tiers.