Hi David, Did read the readme and browsed (too quickly this is why i asked) the code but i'm not sure currently what I get compared to camel+cdi/openwebbeans stack which looks as simple/customizable/flexible and opens the door to k8s native integrations (from healthchecks, metrics, tracing to native mode with graalvm). Any highlights on that? Is the value the python script to help to bootstrap? (if so it would be great to not require pythong for java dev but maybe java?).
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mar. 12 janv. 2021 à 17:55, David Holiday <[email protected]> a écrit : > Hello fellow Camel riders! > > I made a thing for Camel that makes it dead simple for teams to quickly > build and deploy prod-ready microservices. The MVP can be found on github > <https://github.com/davidholiday/kcar>. I'm posting here to ask for your > thoughts on what works, what doesn't, and whether or not you find it > useful. > > I wrote this because I needed a way to quickly produce Camel services. I > needed something that encouraged re-use of service artifacts, didn't rely > on Spring, and could scale in a way that gave me the ability to farm out > work to other engineers without a lot of 'too many cooks in the same > kitchen' bs. > > I'm sure I'm not the first engineer to have these challenges so definitely > curious as to your thoughts not only on the merits of this particular > solution, but also your thoughts and experiences in addressing them. > > cheers (and ty!) > > David >
