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.
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.
Here at Integral Zone we want to ensure we give you the support that you need for your Mule Integration projects to be successful. As part of our portfolio of products, IZ Analyzer, our enterprise-ready Mulesoft code review tool provides a clear business case which we detail here to help you gain the necessary investment …
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.
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.
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 …