Apache Camel is a message routing engine that allows for integration between different components by exchanging messages. It provides a simple way to define routing and mediation rules in a declarative manner. For example, a sample Camel route could read files from a directory and send those files to a JMS queue. Camel is highly flexible and can run in many environments including standalone, OSGi, Blueprint, Spring, and application servers. It has been used by customers for use cases such as building a Netty HTTP gateway with over 100 dynamic routes and load balancing incoming HTTP requests over JMS.

1. Crash course to the
Apache Camel
Brought to you by Henryk Konsek

2. What is Apache Camel?
Messages routing engine.

3. What can Camel do for me?
Integrate components exchanging messages.

4. Camel in a nutshell
From source through processor to
destination.

5. Camel == EIP

6. Camel == gazillion of the connectors
~/projects/camel/components $ ls -l | wc -l
178
Read (write) from (to) JMS, FTP, File system,
SMTP, HTTP...

7. Sample route
from("file:/home/invoices").
to("jms:invoices");

8. Runnable in...
● standalone
● OSGi
● Blueprint
● Spring
● Fabric8 Spring Boot container
● WildFly
● SwitchYard
● More...

9. Customer use case #1
● Netty HTTP Gateway
● routing to the dynamically specified endpoints
● ~100 Camel routes

10. Customer use case #2
● public Jetty HTTP endpoint accepts incoming requests
● Camel acts as the intelligent JMS load balancer

11. Thank you!