Skip to main content Skip to footer

Best Practice

The Throttle Module

Limit the rate of messages for enhanced overview and debugging

Crosser Throttle Module

The Throttle module

Sometimes when you debug Flows that receive data at high rates it is difficult to see what is happening in the debug window. You can of course pause the message updates, but maybe you want to follow the processing over a time period but don’t have to see every individual message. In these cases the Throttle module can be very useful, just as a debugging tool. This module will limit the rate of messages it will let through.

To use it for debugging add it to your Flow and connect it to the module you want to debug. Turn off debugging on the source module and instead enable debugging on the Throttle module. Configure the Throttle module to only pass e.g. one message per second. Then you will get a rate of debug messages that are more easy to follow.



About the author

Goran Appelquist (Ph.D) | CTO

Göran has 20 years experience in leading technology teams. He’s the lead architect of our end-to-end solution and is extremely focused in securing the lowest possible Total Cost of Ownership for our customers.

"Hidden Lifecycle (employee) cost can account for 5-10 times the purchase price of software. Our goal is to offer a solution that automates and removes most of the tasks that is costly over the lifecycle.

My career started in the academic world where I got a PhD in physics by researching large scale data acquisition systems for physics experiments, such as the LHC at CERN. After leaving academia I have been working in several tech startups in different management positions over the last 20 years.

In most of these positions I have stood with one foot in the R&D team and another in the product/business teams. My passion is learning new technologies, use it to develop innovative products and explain the solutions to end users, technical or non-technical."