Welcome to My Integration Journey

When it comes to 2-Way TLS in MuleSoft, many assume that once the DLB (Dedicated Load Balancer) is configured and client certificates are validated — all is secure. But there’s a subtle and important security gap you should know about. 🔍 The Problem: Validation Isn’t Context-Aware Imagine this: Your DLB is set up for 2-Way TLS ✅ You’ve uploaded multiple client certificates to the DLB’s truststore ✅ Everything works — clients can call your APIs over HTTPS using their certificates ✅ But here’s the catch: ...

When building secure APIs, TLS (Transport Layer Security) is a must. But not all TLS setups are created equal. If you’ve ever wondered what exactly two-way TLS is — or when to use it — you’re in the right place. Let’s break it down in a simple way. 🔐 One-Way TLS (Standard TLS) We all use it every day. Every time you log in to your bank account or shop online, you’re using one-way TLS. Your browser verifies the identity of the server via a certificate, usually signed by a trusted Certificate Authority (CA). ...

Setting up 2-Way TLS (mutual TLS) on MuleSoft’s Dedicated Load Balancer (DLB) can feel daunting. We get it — there are keystores, truststores, certs, and configurations across systems. But don’t worry — this guide walks you through it clearly, step by step. 🔧 What You’ll Need Before starting, make sure you have: ✅ A working MuleSoft application deployed to CloudHub ✅ A configured Dedicated Load Balancer (DLB) ✅ Your client certificate (X.509 PEM) ✅ Your truststore (to trust the client’s cert) ✅ Access to Anypoint Platform & Runtime Manager ...

In REST APIs, we often need to get a single resource. In this article, we explore how to structure those GET requests properly. 🧍‍♂️ Get a Single Account by ID To get one specific account, use: /accounts/{id} Example: /accounts/adoe This will return the account with ID adoe. You can apply the same idea to other resources, like: /applications/872233 🧠 Get Resource(s) by Field Value Sometimes you want to retrieve a resource or a small list of resources based on a specific field, like email or region. Instead of creating multiple endpoints, use query parameters. ...

When designing APIs, the GET method is one of the most commonly used HTTP methods. It’s used to retrieve data, either as a full list or a single resource. In this article, we focus on getting collections of resources. 🔍 Use Case Let’s say we’re building a service that allows users to manage accounts. We want to allow users to: List all accounts 📄 Designing the Endpoint Use a plural noun for the resource name: ...

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 characters. Lowercase for the win: URLs can be case-sensitive, so let’s avoid the confusion and stick with lowercase, like /customers/saving-accounts. Extensions are passé: This is the web, not your file system. Drop the .xml and keep it clean with /customers/saving-accounts. URIs Done Right Let’s cut through the clutter when it comes to URIs. ...

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 the error message is structured, how “On Error Propagate” and “On Error Continue” work, and what the default behavior for error handling is. You can read more about error handling in my previous article. For the best user experience, I suggest viewing the infographic on a desktop. ...