Where is the previous stage's data stored when using Round Robin load balancing?

Where is the previous stage's data stored when using Round Robin load balancing?

• A. Object Store
• B. VM Queue
• C. External DB
• D. In-Memory Cache

Answer: (A)

In a distributed setup using Round Robin, the system can pass a request to any member of the cluster, so the data from the previous stage needs a shared place to live until the next step processes it. The Object Store is Mule’s built-in distributed storage that all cluster members can access, making it the right place to persist the previous stage’s data across hops. This allows the next node to retrieve the data regardless of which member handled the prior stage, preserving state in a round-robin flow. VM Queue and In-Memory Cache are local to a single JVM and don’t survive routing to a different cluster member, so they aren’t suitable for cross-node state. An External DB could store data, but it introduces extra latency and management overhead, whereas the Object Store is designed specifically for cross-node, low-latency state sharing in Mule flows.

In a distributed setup using Round Robin, the system can pass a request to any member of the cluster, so the data from the previous stage needs a shared place to live until the next step processes it. The Object Store is Mule’s built-in distributed storage that all cluster members can access, making it the right place to persist the previous stage’s data across hops. This allows the next node to retrieve the data regardless of which member handled the prior stage, preserving state in a round-robin flow.

VM Queue and In-Memory Cache are local to a single JVM and don’t survive routing to a different cluster member, so they aren’t suitable for cross-node state. An External DB could store data, but it introduces extra latency and management overhead, whereas the Object Store is designed specifically for cross-node, low-latency state sharing in Mule flows.