Last Updated on 13/02/2024 by Patryk Bandurski Hey there! Ready to make your API as friendly and reliable? Let’s unpack some RESTful API design practices that are easy to digest and will save you a headache down the road. Dive in for a guide that distills my hands-on experience into practical wisdom for crafting APIs that hit the sweet spot of functionality and user-friendliness. Naming: Clear, Concise Naming your endpoints should be clear-cut and intuitive. Hyphens are your clarity heroes: Separate words for the sake of readability. Go with /customers/saving-accounts rather than a jumble of ..read more

Below is an interactive infographic about the basics of Error Handling in Mule 4. It is a guide that prepares you for MuleSoft Certified Developer – Level 1. You will find here how is error message structured. How do On Error Propagate and On Error Continue works. What is the default behavior for error handling? You can read more about error handling in my previous article. For best user experience I suggest viewing infographic on desktop. Do you like it? Leave the comment and share it with the Community :). The direct link to the infographic is here. The post Error handling Infographic for ..read more

Below is an interactive infographic about the basics of CloudHub Networking. Not sure how to tackle VPC? Where fits shared load balancer or dedicated load balancer? You will find your answers here. Do you like it? Leave the comment and share it with the Community If you like it, you can find here new interactive infographic about error handling in mule 4. The post CloudHub Networking Infographic – easy networking guide appeared first on Mule Blog ..read more

Last Updated on 25/05/2022 by Patryk Bandurski In many projects that I participated in, mutual TLS was a first choice to secure some of the experience APIs. Two-way TLS is great in proving that two sides are known to each other via the exchange of client certificates. Let’s see how it works in CloudHub when we are leveraging Dedicated Load Balancer. Architecture Case In our case, we have MuleSoft Dedicated Load Balancer. The client would like to secure salesforce and payment gateway communication with mutual TLS. As you can see on the diagram below, we have three client certificates installed ..read more

Last Updated on 21/02/2022 by Patryk Bandurski SAP is a well-known company that offers many products, mainly from the ERP domain. It is a matter of time when you need to write an integration with any SAP products. In this article, we do not use any existing connectors like the Mule 4 SAP connector. We consume exposed SOAP Web Service with an asynchronous (one-way) operation. I had some difficulties in this area, mainly focusing on WS-Reliable Messaging. Below, you will find what I struggled with and how I overcame the obstacles. WS-Reliable Messaging Let’s start with a quick reminder of what W ..read more

Last Updated on 14/02/2022 by Patryk Bandurski We are used to designing and exposing REST APIs using Design Center and Anypoint Exchange. MuleSoft is one of the leading middleware vendors that introduced the complete design life cycle. It helped a lot as the majority of the APIs are RESTs. On the other hand, we have event-driven APIs using queues, streams, sockets. So far, we did not have a consistent way to publish such APIs. Fortunately, MuleSoft is evolving, some time ago was added support for Async API in Design Center and Anypoint Exchange. Today I focus on the advantages of the Async API ..read more

Last Updated on 07/02/2022 by Patryk Bandurski On one of the Calicut MuleSoft Meetups, I was presenting the idea of Web Sockets on the MuleSoft platform. To make it more interactive, I prepared a demo application. It was a simple Chat API with a straightforward HTML page to post a message and see chat room messages. Today I want to describe this chat application on a step-by-step basis. This way, you can get hands-on experience publishing and consuming Web Sockets. Not sure what WebSockets are? Read my last article about it. Let’s get started! Scenario The use case is plain and simple. This is ..read more

Last Updated on 16/09/2022 by Patryk Bandurski 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 be achieved using a Dedicated Load Balancer. The ideas presented in the article are based on my real project experience with securing API on CloudHub. API-led layers infrastructure with DLBs On the diagram below you can see my API-led layers ..read more

Last Updated on 30/05/2021 by Patryk Bandurski 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 Load Balancer called URL mapping rules. Mapping API version using DLB Down below, you can see a high-level overview. The consumer is reaching our API via Dedicated Load Balancer. The URL consists of DLB hostname and pattern allowed on ..read more

Last Updated on 30/05/2021 by Patryk Bandurski 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 API versioning in the MuleSoft CloudHub environment. In the end, you should understand how to build an API to enable multi-version deployment. Where to place API version in the URI? It is recommended to use semantic versioning to track the changes we are i ..read more