component-collect) enables high-throughput Fork-Join Parallelism on the visual canvas.
1. How Fork-Join Works in Quixa
1. Multi-Branch Fan-Out (Fork)
When multiple outgoing connection wires are drawn from a single node, Quixa executes those downstream branches concurrently across asynchronous worker threads.2. Multi-Branch Fan-In (Barrier Join)
Wiring all concurrent branches into a Collect Node establishes a synchronization barrier:- The Collect node halts downstream execution until all incoming branches have finished.
- If any branch fails, configurable error handling policies dictate whether to halt or proceed with partial results.
2. Aggregated Output Structure
The Collect node aggregates the responses, status codes, and execution metadata of all incoming branches into a unified JSON object accessible via Response Binding:Accessing Aggregated Values Downstream
Subsequent nodes can consume any branch output using dot notation:3. Configuration Properties
4. Enterprise Use Cases
- Concurrent Risk Verification: Running Fraud Detection, Account Balance, and Compliance Verification simultaneously after customer identification, reducing transaction latency by over 60%.
- Parallel Notification Dispatch: Fanning out to SMS, Email, and Push Notification microservices simultaneously before concluding a transaction flow.
- Multi-Service Catalog Gathering: Fetching product details, real-time warehouse inventory, and personalized user discounts concurrently before assembling the final checkout payload.