MuleSoft Operational and API Management Capabilities

This article will discuss about what are the different operational and API management capabilities provided by the MuleSoft and those can be leverage depending on the client requirements and expectations and that includes Cloudhub (With VPC and Without VPC), Runtime Fabric Manager and Customer Hosted Mule Runtime.

We will be discussing all the operational and API management capabilities with various use cases.

Event Exchange Models in API-Led Connectivity

API-led connectivity forces the architectural restriction that Experience APIs must only invoke Process APIs, Process APIs must only invoke System APIs or other Process APIs, and System APIs must only interact with backend systems. This constraint affects the order and predictability of the interaction patterns in an application network.

When Event-Driven Architecture is applied in the context of API-led connectivity then the application components exchanging events are predominantly API implementations.

Mule4 Automated Policy

Types of Mulesoft Policy


Support for Automated Policies

  • Automated policies are only available for Mule runtime engine (Mule4) APIs using a MuleSoft-hosted control plane.
  • All runtime deployment targets support automated policies (CloudHub, Runtime Fabric, and Hybrid).
  • Automated policies have priority over the same types of policies already applied to a specific API proxy.
  • As an administrator, we can apply policies specific to external identity providers (IdPs, such as OpenID) if the environment to which you want to apply policies includes them.

Steps to Apply Automated Policy

  • In the API Manager, select Automated Policies from the navigation menu on the left.
  • Click Apply new automated policy.
  • Select the provided policy that you want to configure.
  • Apply to a specific set of runtimes.
  • Click Apply.

Select Exchange Policy screenshot

Latency Cost of Implementing API Policies (Anypoint Platform)

Practicing an API policy to API invocations sums treating overhead, which rises in increased latency (decreased response time) as seen by API clients. Depending on the type of API policy, that latency is up to 0.38 milliseconds (approx.) per HTTP request.

Improvement in HTTP request-response latency into the application of several API policies, which are enforced set in the API implementation.

Identify API Policies for All Levels in the Application Network With API-Led Connectivity

Agenda

  • Visit the API policies encouraged out-of-the-box by Anypoint Platform.
  • Decide on one Experience API, one Process API, and one System API from the APIs associated with the "Integration" product.
  • For each of those APIs, pick all API policies that we would advocate applying to that API.
  • Also specify the order for certain API policies.
  • Are there any other API policies that we would want to apply?

Adopting Relevant API Policies for System APIs

Decided C4E establishes the following guidelines for defining API policies on System APIs:

Building HTTPS Proxy With Anypoint API Manager and MuleSoft

Anypoint API Manager has capabilities of enabling the HTTPS proxy by using secrets stored in the Secret Group to build the HTTPS enabled APIs for Cloudhub and Hybrid implementation.

Secret Manager is basically used to store the secret like Keystore, Truststore and configure the TLS context, which can be used with Runtime Fabric and API Manager in Cloudhub.