Mule Bytes: Proxy Vs Auto-Discovery

  • Written By WHISHWORKS
  • 23/02/2018

Proxy: When we are creating a Proxy in API Manager we are adding governance (applying policies, managing traffic, adding authentication methods, etc.) to an API which already exists and it is going to consume 0.1 vCore by default.

There are two main use cases for creating a proxy:

  • When the company has in a SOA implementation and has already created quite a lot of services for which there is no control or governance.
  • When you want to expose data externally and deploy the proxy in a DMZ following the Gateway pattern.

Auto-Discovery: API auto-discovery is the mechanism to manage an API from API Manager by pairing the deployed application to an API created on the platform, regardless of how it was deployed. Auto-discovery will not consume extra cores since you manage the Mule API directly.

For more information please look at the post https://mulesoftpartners.bloomfire.com/posts/1518177-flash-concepts-api-manager-api-auto-discovery-vs-api-proxy

If you would like to find out more about how Systems Integration could help you make the most out of your current infrastructure while enabling you to open your digital horizons, do give us a call at +44 (0)203 475 7980 or email us at marketing@whishworks.com

Other useful links:

What is an API and how does it enable Connectivity?

API Recipes with MuleSoft Anypoint Platform

MuleSoft Integration Services

Latest Insights

WHISHWORKS - MuleSoft API integration for Universities
Blogs

API-led connectivity for Universities

An architectural approach to API-led connectivity that enables hybrid, multi-modal learning and teaching experiences for universities.

Salesforce FSC - Leads and Referrals
Blogs

Salesforce FSC – Leads and Referrals

In this blog we look at how Leads and Referrals work in Financial Services Cloud and how they’d make sense within a banking environment.

evented APIs
Blogs

What are evented APIs?

We can think of an evented APIs as the fabric that binds and integrates all the applications in an event-driven architecture.