anchor.diff:  :since: 
   :supportlevel: Stable
   
  -Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the xref:enterprise-integration-patterns.adoc[EIP patterns] in various ways.
  +Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters]
  +from the xref:enterprise-integration-patterns.adoc[EIP patterns] in various ways.
   
   image::eip/PipesAndFilters.gif[image]
   
  -With Camel you can split your processing across multiple independent processing
  - which can then be chained together in a logical unit as a step.
  +With Camel, you can group your processing across multiple independent EIPs
  +which can then be chained together in a logical unit, called a _step_.
   
   A step groups together the child processors into a single composite unit.
   This allows to capture metrics at a group level which can make management and monitoring
   of Camel routes easier by using higher-level abstractions. You can also
  -think this as a middle-level between route vs each individual processors in the routes.
  +think this as a middle-level between the route and each individual processors in the routes.
   
  -You may want to do this when you have large routes and want to breakup the routes into
  +You may want to do this when you have large routes and want to break up the routes into
   logical steps.
   
   This means you can monitor your Camel applications and gather statistics at 4-tiers:
  
positive.code:   </step>
  </route>
  ----
  
negative.code:       .bean("foo")
        .to("acitvemq:OutputQueue")
      .end()
      .to("direct:bar");
  ----
  
  As you can see this groups together `.bean("foo")` and `.to("acitvemq:OutputQueue")`
  into a logical unit with the name foo.
  
  In XML you use the `<step>` tag:
  
  [source,xml]
  ----
  