If you want to follow the API-led principles your process and system APIs should not be accessible from outside. These APIs are only for internal usage. On top of them, other APIs are built and the application network grows. Experience APIs should be available for consumers to use. Today I show you how can it…
Integration Architecture
How to map your API version using DLB?
In the last article, I described two scenarios of API versioning for the CloudHub environment. I recommended embedding the API version in the application name to allow easily deploying multiple versions of the API at the same time. Did you know that we can even improve that approach? We can use a feature of Dedicated…
How to version an API to easily deploy many versions?
We version the APIs to track the changes we made to them. Most of the time, it is sufficient to host just a single, major version of the API. However, there are cases when we need to host the previous version for backward compatibility reasons. In this article, I decided to share my thoughts on…
Introducing fault tolerance using Until Successful scope
Our APIs should be fault-tolerant. We have many strategies to cope with this. Previously I described a possible scenario with a circuit breaker pattern. Today I remind you of another, simpler way. Retry! We can retry the operation a couple of times before using a different fault tolerance pattern or stopping processing the message. Let’s…
JWT Validation policy and salesforce named credentials
In the last article, I described how to secure your services with the JWT Validation policy. To test it, I used Salesforce hands-on org from the trailhead. Imagine now that the Salesforce developer or admin reaches you and is asking you some questions about named credentials to set up JWT header. To make it smooth,…
Secure calls from Salesforce to MuleSoft with JWT
A couple of my last articles focuses on connectivity between Salesforce and MuleSoft. This will be the next article in the series. In many cases, we would like to set up as secure communication as possible. We can start by enabling secure HTTP traffic, then sending a basic authorization header. How about sending a signed…
Why Salesforce can’t connect to my API over DLB?
Last time I described connectivity scenario when Salesforce was reaching MuleSoft API exposed via Shared Load Balancer. What do we need to take into consideration when we slightly change our infrastructure and purchase a Dedicated Load Balancer? There are some vital changes that we should be aware of. In this article, I point out at…
Publish API via CloudHub for Salesforce – connectivity test
Once we develop and deploy our MuleSoft applications, it is a good idea to test the connectivity. Is the calling system able to reach our API and receive a response? In this article, I will focus on the case when I expose API to Salesforce. I will use the Salesforce playground that is available on…
How to enable dedicated load balancer under own domain
A Dedicated Load Balancer is an optional component of the Anypoint Platform. Unlike the Shared Load Balancer, this one gives greater flexibility and possibility to configure. In this article, you will find the answers to three questions: Why use a DLB? How does it work? And finally, how to configure it work with our domain….
Publish web socket in the experience layer
Some time ago, MuleSoft introduced Web Socket Connector. In this article, I briefly describe what web socket gives us in the context of integration. The main focus of the article is to show you how to publish a web socket for your consumers. Web Socket So the first question is what a web socket is….