Round Robin In Mule 4

What Is Round Robin?

In the round-robin arrangement, we will choose all the elements with equal rational order i.e with the same difference between any two elements in a group.

If we consider a real-time scenario of a computer operation, different processes of a program using the same method will often process for a specific time period and then leaves the thread of that process to be used by another process of that method.

Real-World Example:

Round Robin in MuleSoft:

The Round Robin switch repeats through a rundown of at least two routes altogether, yet it just routes to one of the routes each time it is executed. It monitors the recently chosen route and never chooses a similar route successively. For instance, the first run through Round Robin executes, it chooses the primary route. Whenever it chooses the subsequent route. On the off chance that the recently chosen route is the last route in the rundown, Round Robin bounces to the primary route.

How to get Round Robin in Mule 4:

Step 1:

In Anypoint Studio, click the Search tab in the pallet and type the module name (round robin).

Step 2:

Click the module and drag it into the canvas.

Example for Round Robin in Mule 4: 

Using the scheduler component to develop a round-robin process based on cron expression.

Please follow the below steps:

Step 1:

Create a New Mule Project as Shown Namely as Round_Robin.

Step 2:

Drag and drop a Scheduler component to get a request for your servers.

Step 3:

In that scheduler, we can choose any of the Scheduling Strategy's i.e

1. Fixed Frequency

2. Cron

Cron is a broadly utilized standard for depicting time and date information. The Scheduler monitors each second and makes a Mule occasion when the Quartz Cron articulation coordinates your time-date setting. You can trigger the occasion only a single time or at ordinary interims.

A date-time articulation comprises of six required settings and can incorporate the discretionary year setting. You indicate the settings in the accompanying request:

• Seconds (0-59)
• Minutes (0-59)
• Hours (0-23)
• Day of month (1-31)
• Month (1-12 or JAN-DEC)
• Day of the week (1-7 or SUN-SAT)
• Year (empty or a 4-digit year between 1970-2099, for example, 2019)

Here are a few examples

Note:

The Scheduler component also supports Quartz Scheduler's special characters.

• *: All values
• ?: No specific value
• -: Range of values
• ,: Additional values
• /: Incremental values
• L: Last day of the week or month, or last specific day of the month (such as 6L for the last Saturday of the month)
• W: Weekday, which is valid in the month and day-of-the-week fields
• #: Nth day of the month. For example, #3 is the third day of the month

As per example, I choose Cron Scheduling Strategy

Note:

As per Cron Expression (* * * * * ?), Every second it will be Restart the service

Step 4:

Now, drag and drop the Round Robin component from the Mule Palette on to the Designed Canvas.

Step 5: 

Next, take two loggers for checking the techniques of the round-robin.

Logger1 as Route-1

Logger2 as Route-2

Now, we look about the entire flow of the project as below

Step 6:

Run the Project

Example 

xxxxxxxxxx

<mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd">

    <flow name="round-robinFlow" doc:id="d9f11a6d-a205-4905-9057-7b05bb966737" >

        <scheduler doc:name="Scheduler" doc:id="007323e7-31df-42f1-ae76-4032a0e5b58a" >

            <scheduling-strategy >

                <cron expression="* * * * * ?" timeZone="Asia/Kolkata" ></cron>

</scheduling-strategy>

        </scheduler>

        <round-robin doc:name="Round Robin" doc:id="b831ff15-cf36-450f-ba64-f7cdd16b43a4" >

            <route>

                <logger level="INFO" doc:name="Logger" doc:id="347412e7-9028-4936-b11f-13624b3d9ab6" message="Route1"></logger>

            </route>

            <route>

                <logger level="INFO" doc:name="Logger" doc:id="abd1b4cd-fdb9-497c-b8d3-8a21f8ac1acb" message="Route2"></logger>

            </route>

        </round-robin>

    </flow>

</mule>

Note:

In the model over, the first run through the Round Robin is executed it prints Route-1. Whenever it prints Route-2. The third time, since there are just two routes, Round Robin begins again with the principal route and prints Route-1.

Thanks for reading!