Content:

Most companies run several software products from different vendors in their day-to-day business. These applications may have different purposes, data storage and operating methods. This usually leads to data silos where data is either duplicated between databases or available in one database but not in another. As a result, companies complain about data inconsistency, slow process turnaround times, lack of early detection of changes in the business environment (customer behaviour), etc.

As a solution approach, integration architectures are designed that integrate the originally isolated applications (e.g. ERP, CRM...) with each other, bridging content and technological gaps.
Apache Camel is a lightweight and flexible open source framework for the integration of self-contained applications, which supports the development of integration architectures. Camel's strengths include the availability of various DSLs (Domain Specific Language) for describing routes and support for numerous enterprise integration patterns. Camel is also characterised by the fact that it can be embedded in all relevant ecosystems, such as Spring Boot, Quarkus, various application servers and Kubernetes.

After a short introduction to the problems of self-contained application systems, the following topics will be addressed:

- Requirements for an integration architecture and possible solutions (point-to-point, hub-and-spoke, enterprise service bus, etc.).
- Basic concept and architecture of Apache Camel
- Overview: Runtime environments for Apache Camel (standalone, embedded in various containers or in the Spring Boot Ecosystem)
- Camel DSL (Domain Specific Language) with focus on Java
- Selected Camel components
- Selected Camel data formats
- Enterprise Integration Patterns and their support by Camel
- Error handling and monitoring with Camel
- Outlook: Apache Camel K (runs natively on Kubernetes and supports serverless and microservice architectures).

We focus on a specific set of topics to look at and understand in detail

Disclaimer: The actual course content may vary from the above, depending on the trainer, implementation, duration and constellation of participants.

Whether we call it training, course, workshop or seminar, we want to pick up participants at their point and equip them with the necessary practical knowledge so that they can apply the technology directly after the training and deepen it independently.