Devoxx MA - Connecting disparate systems in a lightweight way

Have you ever struggled with connecting systems that were not designed to communicate with each other? This is a common challenge faced by many microservices architectures today. In this talk, we’ll explore some of the tools and approaches that can help you break down these silos and integrate your microservices with external systems seamlessly, allowing for faster development cycles and more efficient integration.

We’ll start by introducing Apache Camel, a powerful tool that offers over 300 connectors to transfer data between a wide variety of systems. With its rich set of routing, filtering, and transformation capabilities, Camel is a versatile system integration tool that can help you integrate your systems more efficiently.

Next, we’ll dive into developing a Java application that can seamlessly connect various systems using Apache Camel. With just a few lines of code, we can utilize the power of Camel to transform and transfer data between different systems. Furthermore, we’ll explore how Camel JBang and Quarkus can greatly improve the developer experience.

By the end of this talk, you’ll have the tools and knowledge to connect your Java microservices with external systems faster and more efficiently.

Transcript

1. Connecting disparate systems in a lightweight way Zineb Bendhiba Devoxx Morocco October 2023
2. Integration challenges
3. Zineb Bendhiba • Senior Software Engineer at Red Hat • Apache Camel PMC • International Speaker • 15+ years professional software development experience • Speak English, French, Moroccan Darija, Arabic • Cadi Ayyad University Alumn • https://zinebbendhiba.com
4. 1 Connecting to disparate systems
5. Challenge #1 : Connecting to disparate systems
6. Challenge #1 : Connecting to disparate systems
7. Challenge #1 : Connecting to disparate systems
8. Challenge #1 : Connecting to disparate systems
9. Challenge #1 : Connecting to disparate systems
10. Challenge #1 : Connecting to disparate systems
11. Challenge #1 : Connecting to disparate systems
12. Apache Camel can set you free
13. Apache Camel can set you free
14. What is Apache Camel ?
15. Apache Camel is an Open Source Integration Framework
16. Entreprise patterns Emergent “Design patterns” best practices
18. Apache Camel: Camel message Routing Term Meaning Message data transferred by a Route Exchange envelope; wraps the data Endpoint a channel, receiver or sender Component know-how; creates endpoints Processor Java API; custom logic
19. Apache Camel: Domain Specific Language (DSL) from(“aws-s3:myBucket”) .to(“http:my-host/api/path”) Libraries POJO Biz Logic...
20. Apache Camel: Domain Specific Language (DSL) from(“aws-s3:bucketName”) .to(“http:my-host/api/path”)
21. Apache Camel: Domain Specific Language (DSL) from(“kafka:topicName”) .to(“ftp:host:port/directoryName”) Libraries POJO Biz Logic... from(“kafka:topicName”) .to(“aws2-s3://bucketName”)
22. 2 Data Transformation
23. Using Apache Camel Data formats
24. Using Apache Camel Data formats from(“kafka:topic”) .unmarshal().json() .to(“http:my-host/api/path”)
25. Using Translator or Set Body from("direct:cheese") .transform(new DataType("myDataType")) .to("log:hello"); from("direct:cheese") .setBody(simple("Hello ${body}")) .to("log:hello");
26. Using template based components from("direct:cheese") .log("Received XML: ${body}") .to("xslt:classpath:xslt/transform.xsl") .log("Transformed XML: ${body}");
27. Using Processor from("activemq:myQueue") .process(new Processor() { public void process(Exchange exchange) throws Exception{ String payload = exchange.getIn().getBody(String.class); // do something with the payload and/or exchange here exchange.getIn().setBody("Changed body"); } }) .to("activemq:myOtherQueue");
28. Using Beans from("activemq:myQueue") .process(new Processor() { public void process(Exchange exchange) throws Exception{ String payload = exchange.getIn().getBody(String.class); // do something with the payload and/or exchange here exchange.getIn().setBody("Changed body"); } }) .to("activemq:myOtherQueue");
29. Using Bean package com.foo; public class MyBean { public String saySomething(String input){ return "Hello " + input; } } from("direct:hello") .to("bean:com.foo.MyBean");
30. Content Enricher from("seda:a") .to("direct:myEnrichEndpoint") .to("seda:b");
31. 3 Routing Messages
32. Content Based Router from("seda:a").choice() .when(header("foo").isEqualTo("bar")).to("seda:b") .when(header("foo").isEqualTo("cheese")).to("seda:c") .otherwise().to("seda:d");
33. Message Filter from("seda:a") .filter(header("foo").isEqualTo("bar")).to("seda:b");
34. Recipient List from("seda:a") .to("seda:b", "seda:c", "seda:d");
35. Load Balancer from("direct:start") .loadBalance().roundRobin() .to("mock:x", "mock:y", "mock:z");
36. Idempotent Receiver from("direct:performInsert") .idempotentConsumer(header("id")).idempotentRepository("insertDbIdemRepo") // once-only insert into database .end()
37. Using others EIPs
38. Demo #1
39. Demo #1
40. Additional Challenges
41. 4 Logging
42. Logging • Logging Components • Log EIP • Customizing logs and format • Masking sensitive information from("activemq:orders") .to("log:com.mycompany.order?level=DEBUG&groupSize=10") .to("bean:processOrder"); from("direct:start") .log("Processing ${id}") .to("bean:foo");
43. 5 Error Handling
44. Error Handler: Dead Letter Queue from("direct:start") .to("direct:invalidEndpoint"); // This will trigger an error // Configure the Dead Letter Channel (DLC) to handle errors errorHandler(deadLetterChannel("direct:errorQueue") .maximumRedeliveries(3) // Maximum number of redelivery attempts .redeliveryDelay(1000) // Delay between redelivery attempts .logExhausted(true) // Log if redelivery attempts are exhausted ); // Define the DLC route to handle failed messages from("direct:errorQueue") …;
45. Demo #2
46. Demo #2
47. ارﻛﺷ ThankYou