Best Practices for Middleware and Integration Architecture Modernization with Apache Camel

What are important considerations when modernizing middleware and moving towards serverless and/or cloud native integration architectures? How can we make the most of flexible technologies such as Camel K, Kafka, Quarkus and OpenShift. Claus is working as project lead on Apache Camel and has extensive experience from open source product development.

[ClausIbsen]

Its now 3 years since this video was created. I wonder if there is interrest for an updated video, and if so is there any content that is more relevant today to focus on or any idea of what to include?

And is the 30 minute length too long?

[dixiesebastianappan]

Awesome. As usual crisp. To the point.

[m_]

when we migrate old application to new java modern architecture or cloud native, any best practice about Direct and SEDA component migration ? replace with event message such as Kafka in order to split monolithic application into microservices ?

[ShoaibKhan_iamsrk]

Hi Claus, just wanted to understand if Camel K can be used for full integrations as we do currently with Java DSL in spring boot? Most of the examples refer to single file with few routes when it comes to Camel K. How about integrations which spans across multiple Java files with processors, routes, domain models defined in separate files? What would be the best approach to migrate such spring boot based camel projects to Camel K?

[satish]

Can we replace Camel with Kafka? is it the right use case?