Build a Query in MuleSoft With Optional Parameters

In this tutorial we will see how to:

  • Define a RAML API specification to search products in a catalog database
  • Establish and configure a database connection to query a MySQL database
  • Build a query to support multiple optional filters
  • Add optional sorting capabilities to our query at DB level

1. Define the RAML of a Search API

Imagine that you want to create a MuleSoft API to search products inside a catalog. This API will need to accept multiple filter parameters and an optional sorting parameter. All these parameters can be optional and will be used to generate a dynamic query to search products in your catalog database.

Strict Validations in Mulesoft APIkit Router

This article will help you in your understanding of the functionality of Query Parameters and Headers Strict Validations in the MuleSoft APIkit Router.

What Are Strict Validations?

Strict Validations is an APIkit router configuration that restricts or limits API calls with unwanted Headers and/or Query Parameters which are not defined in the API Specification (RAML).

Mule Standalone Runtime Setup and Deployment

When most of the integration data is lying inside an organization's data center and data is highly secured, then the On-Prem deployment model is the right solution.

It does offer the flexibility to set up your load balancing, domains, VPC, and anything you want to do to your environment as you will be building it in your own data center. You can cluster specific servers that you have in your infrastructure and set them accordingly.

How to Learn MuleSoft: An Exciting and Viable Career Option on the Brink of Digital Evolution

Nature has a way of forcing evolution, requiring one field after the next to transform in an attempt to stay competitive and viable. As mankind branches out further into the depths of complicated technological processes, so do the tools that help reach new heights; and at the forefront is technology. Businesses around the world are starting to follow their breathing counterparts, transforming into seemingly solo-functioning entities where little to no human interference is required.

Thanks to MuleSoft, businesses have more freedom and creativity in their hands than ever before, using the application building platform to increase client connection and overall productivity. No longer is there a need for separate clouds and bulky connectors to create the perfect workflow. MuleSoft essentially blurs the lines and borders traditionally set by separate systems allowing them to communicate seamlessly in a matter of seconds.

Create a Custom Connector Using XML SDK and Deploy it in Anypoint Exchange

Introduction

XML SDK is an alternative approach to build custom modules in Mulesoft. This approach is comparatively easier to build compared to the already existing JAVA Mule SDK. Creating a custom module in Mule SDK is similar to creating a Mule application. This document is focused on demonstrating the steps to build a custom module using the XML SDK and deploying it in Anypoint Exchange. We will create a custom connector in Mule 4 that will perform basic arithmetic operations like addition and subtraction

Requirements

Application/Service

Fine-Grained vs. Coarse-Grained APIs in MuleSoft

API design is a fascinating topic. One important aspect of API design is determining the right 'size' of an API in terms of its features and functionality. All architects must have grappled with this issue at some point or the other. In this article, I will try and give some insights into the various parameters that we need to think through before arriving at the 'right' grained API:

  • Maintainability: The first aspect that comes to mind is the maintainability of APIs. Coarse-grained APIs are difficult to maintain. As the API consumer needs grow, it will be difficult to add more implementation variations or parameters.