janihur commented on issue #163: URL: https://github.com/apache/camel-kit/issues/163#issuecomment-6851977666
I'm evaluating Camel and have no previous Camel code base, so I'm sorry I don't have any real production-grade examples. The most elaborate scenario so far is the following demo, done in two steps with two Camel Kit pipelines: 1. Observability demo with a mixture of several simple Camel applications and Kafka, without payload logging/storage. 2. Add payload logging to a separate payload archive (i.e. payloads not visible in application logs). Step 2 affected almost every route (integration entry points), and major new components and patterns appeared. Camel Kit did the job but was a bit clumsy here and there, and IIRC the decisions made in step 1 but reverted in step 2 kept resurfacing. In the end I had two sets of pipeline docs, but neither described the system completely and correctly. From prior experience, substantial changes are mainly for integration applications with major orchestration responsibilities. In these scenarios we would usually like to evolve the existing application, not to rewrite everything from scratch. These kinds of applications are rare, but they do exist, in my experience, YMMV. It would be supercool if there were a document similar to Kit's design-spec.md but up to date with the implementation. I don't like the "amendment" concept that seems to describe a change on top of the baseline. Cumulative amendments just make documents hard to understand. It is unclear if `design-spec.md` should be kept up to date with "minor" changes or not. Also, having some pipelines describing greenfield development and some describing a change set on top of that looks confusing. From my evaluation perspective, a good first step is just to clearly describe the current limitations and future directions. I see you already have #164, so I'm following that closely and this issue can be closed on my side. I'm planning to use and keep up with the latest Camel LTS. Runtime is not yet settled but started demos with Camel Main (because Camel CLI), but production runtime will run either Spring Boot or Quarkus. Route DSL is YAML. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
