Skip to main content

Keep Complexity Low

While it is possible to achieve many things in one very long and complex Route, it makes it very hard to read and leaves the Route prone to unhandled errors. If your Route becomes complex, try to break it down into several subRoutes. Remember when doing this that you may need to keep control of the order of processing, so use suitable endpoints (“direct” for synchronous behavior and “seda” for asynchronous behavior).

SubRoutes should be ordered in the order in which you expect them to be processed from top to bottom going from left to right. The main Route (usually the Route that receives the initial message) should be at the top of the Route design.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!