anchor.diff:  </route>
   ----
   
  -== Asynchronous delaying
  +=== Asynchronous delaying
   
  -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.
  +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.
  +
  +In Java DSL you enable asynchronous delaying using `asyncDelayed` as shown:
   
   [source,java]
   ---------------------
  
positive.code:   .throttle(100).asyncDelayed()
    .to("seda:b");
  ---------------------
  
negative.code: :since: 
  :supportlevel: Stable
  
  How can I throttle messages to ensure that a specific endpoint does not get overloaded, or we don’t exceed an agreed SLA with some external service?
  
  image::eip/MessagingAdapterIcon.gif[image]
  
  Use a Throttler that controls the rate how many or fast messages are flowing to the endpoint.
  
  == Options
  
  