Skip to main content

Next Hop Routing

Some plugins, such as Timer or Switch, include a Next Hop configuration.

Next Hop defines which component a message should go to next immediately after processing, without using a queue. This makes it a synchronous routing mechanism.

How Next Hop Works​

  • After the plugin processes a message, it is sent directly to the configured next plugin
  • The message does not go through a queue
  • The next plugin must accept the current message

Use case:

  • Simple, linear workflows where messages are processed step-by-step without delay
  • When messages do not need to be stored or retried

Configuring Next Hop​

To configure Next Hop:

  1. Open the plugin configuration that supports next hop (e.g., Timer, Switch)
  2. Locate the Next Hop field
  3. Select the destination plugin that should receive the message next

Tip: Next Hop is ideal for workflows that need fast, sequential processing without queueing.

Best Practices​

  • Use Next Hop for linear, synchronous flows
  • Use queues if you need:
    • Asynchronous processing
    • Retry on failure
    • High reliability and no message loss