Skip to site navigation (Press enter)

[CONF] Apache Camel > Throttler

confluence Fri, 02 Jul 2010 06:31:00 -0700

     Throttler
    Page edited by             Claus Ibsen
    
        

                         Changes (2)
                                 
    

            
            ...

             
{code} 

            from("seda:a").throttler(100).to("seda:b"); 

            {code} 
 

            ...

            {snippet:id=example|lang=xml|url="" 
 

            h3. Asynchronous delaying 
*Available as of Camel 2.4* 
 
You can let the [Throttler] use non blocking asynchronous delaying, which means Camel will use a scheduler to schedule a task to be executed in the future. The task will then continue routing. This allows the caller thread to not block and be able to service other messages etc. 
 
{code} 
from("seda:a").throttle(100).asyncDelayed().to("seda:b"); 
{code} 
 

            {include:Using This Pattern} 

        
                            Full Content
                    
        Throttler

The Throttler Pattern allows you to ensure that a specific endpoint does not get overloaded, or that we don't exceed an agreed SLA with some external service.

Using the Fluent Builders


from("seda:a").throttle(3).timePeriodMillis(10000).to("log:result", "mock:result");


So the above example will throttle messages all messages received on seda:a before being sent to mock:result ensuring that a maximum of 3 messages are sent in any 10 second window. Note that typically you would often use the default time period of a second. So to throttle requests at 100 requests per second between two endpoints it would look more like this...


from("seda:a").throttle(100).to("seda:b");



For further examples of this pattern in use you could look at the junit test case

Using the Spring XML Extensions


<route>
  <from uri="seda:a" />
  <throttle maximumRequestsPerPeriod="3" timePeriodMillis="10000">
    <to uri="mock:result" />
  </throttle>
</route>



Asynchronous delaying
Available as of Camel 2.4

You can let the Throttler use non blocking asynchronous delaying, which means Camel will use a scheduler to schedule a task to be executed in the future. The task will then continue routing. This allows the caller thread to not block and be able to service other messages etc.


from("seda:a").throttle(100).asyncDelayed().to("seda:b");



Using This Pattern

If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.
    
        
        
            Change Notification Preferences
        
        View Online
        |
        View Changes
                |
        Add Comment
 ...
 {code}
 from("seda:a").throttler(100).to("seda:b");
 {code}
 ...
 {snippet:id=example|lang=xml|url=""
+h3. Asynchronous delaying 
*Available as of Camel 2.4* 
 
You can let the [Throttler] use non blocking asynchronous delaying, which means Camel will use a scheduler to schedule a task to be executed in the future. The task will then continue routing. This allows the caller thread to not block and be able to service other messages etc. 
 
{code} 
from("seda:a").throttle(100).asyncDelayed().to("seda:b"); 
{code}
 {include:Using This Pattern}