Thomas, over the many years I have watched your teams videos on integration and its always professional and honest review. Thanks for taking an eye on Camel again, and what the low-code UI Karavan can do. Its fantastic work by Marat. The Camel project itself (in particular camel-core) provides a lot of structured information for tooling (also 3rd party) and that is what makes Karavan possible. As you say in the video. The UI is 100% standard Camel and as Marat has said Karavan is a "Visual DSL of Camel". The output of Karavan is 100% files that can run in Camel (camel-main, camel-spring-boot, or camel-quarkus) with anything else (no Karavan, or other products). That separation is very important IMHO; which makes gitops possible and for anyone to build and deploy Camel as they need. And your team is surely welcome to take a look at camel jbang (its a power tool) that can make you 10x faster and better with Camel. Its a bit hard to explain but when you got started using it, you would not go back. I personally use it every day and makes me a lot more productive.
Karavan or KAOTO which one is better for using Camel 4 version? What is the difference between Karavan and KAOTO as both are Low Code No code visual editor for Apache Camel?
Good question. The visual editor of Karavan looks to me very similar to Kaoto. Maybe they share even common code but I do not know. Karavan provides not only an editor but also runtime support. I have the impression that Karavan is more mature but maybe I am wrong and I cannot tell which one is better. Because they share the same file format and components it is possible to exchange editors without any modification. Maybe you can share your experience with tools.
Thomas, over the many years I have watched your teams videos on integration and its always professional and honest review. Thanks for taking an eye on Camel again, and what the low-code UI Karavan can do. Its fantastic work by Marat.
The Camel project itself (in particular camel-core) provides a lot of structured information for tooling (also 3rd party) and that is what makes Karavan possible. As you say in the video. The UI is 100% standard Camel and as Marat has said Karavan is a "Visual DSL of Camel". The output of Karavan is 100% files that can run in Camel (camel-main, camel-spring-boot, or camel-quarkus) with anything else (no Karavan, or other products). That separation is very important IMHO; which makes gitops possible and for anyone to build and deploy Camel as they need.
And your team is surely welcome to take a look at camel jbang (its a power tool) that can make you 10x faster and better with Camel. Its a bit hard to explain but when you got started using it, you would not go back. I personally use it every day and makes me a lot more productive.
Vielen Dank für das informative Video. Lohnt sich wirklich es sich mal tiefer anzuschauen wie es scheint.
Erinnert mich stark an Node-RED. Jedenfalls interessant
Tolles Video! Ja bitte jbang vorstellen.
Wir haben eine Camel-Schulung für unsere IPaaS-Initiative die auch auf Karavan basiert bei Predic8 konsumiert und ich kann sie nur empfehlen.
Karavan or KAOTO which one is better for using Camel 4 version? What is the difference between Karavan and KAOTO as both are Low Code No code visual editor for Apache Camel?
Good question. The visual editor of Karavan looks to me very similar to Kaoto. Maybe they share even common code but I do not know. Karavan provides not only an editor but also runtime support. I have the impression that Karavan is more mature but maybe I am wrong and I cannot tell which one is better. Because they share the same file format and components it is possible to exchange editors without any modification. Maybe you can share your experience with tools.