Hello, Kamelets are becoming an important and universal higher-level components / building-blocks of Apache Camel; that are universal usable in all of Camels runtimes and projects, whether its Camel on Spring Boot, Camel Standalone, Camel Kafka Connector, Camel Quarkus, Camel JBang and Camel K as well.
In the beginning kamelets were just tied to Camel K and therefore they were documented and released through the Camel K subproject. The situation is now really different. Camel-Kamelets and the kamelets catalog is now part of the full chain of Camel releases. I personally have some ideas around it. In my opinion camel-jbang should be the starting point for developing a camel application: Kamelets could be an extremely important accelerator in the getting started experience. - Install camel-jbang - Select your Kamelet for source and sink - run your integration - It works? Cool. It doesn't work? Let's see why - My integration is now stable, I want to pass to another level. I could still use the kamelets, but also I could switch to a full Camel route. Let me select my runtime: Quarkus, Spring Boot, Camel K or plain camel. Let me export the project to my selected runtime. - Ready to go. All of this could also pass through Camel-Karavan, without touching code, or touching very few lines of code. We have really a lot of power and a lot of stuff to improve. In my opinion we should work on multiple sides: - make it possible to load different kamelet catalogs (complex cases, custom kamelets, etc.) - improve the default Kamelets catalog - Focus on the camel-jbang experience - Maybe try to think about a Kamelets Marketplace or catalog marketplace My proposal is also to note in terms of documentation that kamelets are not only tied to Camel K, but some fundamental building block in the Camel experience. I think we should create some epic around this and try to follow this path. Any feedback, comments and thoughts are welcome. Please let me know what you think. Cheers, Andrea
