Skip to content

Instantly share code, notes, and snippets.

@khalidabuhakmeh

khalidabuhakmeh/azureapi.md

Created December 22, 2018 15:00
Show Gist options
  • Save khalidabuhakmeh/b70b981741b1d341823e1fe5a3ef1c39 to your computer and use it in GitHub Desktop.
Save khalidabuhakmeh/b70b981741b1d341823e1fe5a3ef1c39 to your computer and use it in GitHub Desktop.
Download ZIP
Azure API Management Questions
Raw
azureapi.md

Azure API Management Questions

App Assumption

We are building an ASP.NET Core API. We would like our API to have the following advantages:

  • Infrastructure
  • Caching (Server and Client Side)
  • Scaling / Performance
  • Security
  • Throttling
  • CORS
  • Custom Domains and SSL

Infrastructure

When you import an API into API Management, is importing more of a placeholder or does it manage the backing service as well (App Service). When in Azure, should you push all your APIs to an internal network so that only other Azure services can talk to your APIs? This effectively makes the Azure API Management service your public API service area.

Caching

We want to cache on the server and on the client, utlizing various criteria. We can do this via Cache Policies.

Scaling

It seems like scaling is more focused on scaling the Azure API management instance (proxy), and scaling of your backend services would have to be done seperately.

Security

We are using IdentityServer, you can configure your security to use it via the OAuth 2.0 spec.

Throttling

Throttling and control can be done via a throttling policy.

CORS

Because our Frontend developers couldn't function without CORS.

Custom Domains

Is a custom domain per API management service instance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment