In this read, I have attempted to highlight basic features that should be present in every System API. A poorly designed System API will always need enhancements or other process/experience APIs built on top of it, to get the best out of it.
Okta is chosen as external client management to create dynamic client applications and grant, authorize and introspects tokens using Okta. The role of Okta includes creation of Client Id and Client Secret, as well support for OAuth flows – Authorization code and client credential.
Out of all the concepts, best practices, and principles that are talked about an API and its design, the one that usually given the lesser importance is an API error response. A part reason for this shortcoming is that everyone is happy till the time API is working fine. So lets put little thought into how should we treat the failure of an API function.
Learn to develop SOAP Web Services using Mule, deploy it on Anypoint Runtime Manager and manage the deployed Web Services using Anypoint API Manager by applying policies.
Visualize your application network using Anypoint Visualizer. Explanation with System APIs, Process APIs and Experience APIs
MuleSoft has a few offerings in terms of hosting. For the purposes of this blog, I would like to class them as Cloudhub hosted or non-Cloudhub hosted.
Cloudhub provides a bursting option only for 0.1 and 0.2 vCores. The reason for this classification is to compare like for like performance between the MuleSoft Managed Cloudhub option against the non-Cloudhub hosted option, specifically in the bursting context.
This blog explains how external applications can connect and consume Anypoint Platform APIs using the new Connected Apps feature.
Using Connected Apps, users can delegate their access to external applications without sharing their credentials. Delegated access can be revoked by the user at any point.
With the API economy being a key enabler for turning your business or organisation into a platform, most organisations have started to roll out APIs.
This is part two of the three blog series on Anypoint VPC. You can checkout other two blogs like What is Anypoint VPC(Virtual Private Cloud)? and Connecting Anypoint VPC to Customer On-Premise. In this blog we will try to explore all the aspects around sizing of Anypoint VPC with relevant examples. Why consider Sizing at …
Anypoint VPC is no different than any other VPC out there with the exception that it is only for running the Mule applications of an organization. To understand and decode what an Anypoint VPC is, we first need to understand what a VPC is in generic terms. This is part one of a three part …
Continue reading “What is Anypoint VPC(Virtual Private Cloud)?”
This is part three of the three blog series on Anypoint VPC. You can checkout other blogs about What is Anypoint VPC(Virtual Private Cloud)? and Sizing of Anypoint VPC. All organizations have an on-premise network in some form or the other. These group of private networks/servers run a lot of internal and legacy applications. These …
Continue reading “Connecting Anypoint VPC to Customer On-Premise”
Mulesoft is an industry leader in the API management and iPaaS segment. An increasing number of companies are working with Mulesoft products for all their integration needs. This means more and more APIs and integration implementations are added into the enterprise’s backlog. But what about MuleSoft Code Quality? Since we use an industry leading integration …
