tadayosi commented on issue #1044:
URL:
https://github.com/apache/camel-kafka-connector/issues/1044#issuecomment-782804218
I think it's a great discussion. Personally what @oscerd and @orpiske
explained really makes sense: CKC is the complehensive collection of generic
Kafka connectors abstracted away from the implementation by Camel. It's a
great, focused strategy for the project. Here are some constructive suggestions
from me in this perspective:
1. At the same time, what @ffang expected with CKC shouldn't be uncommon
among users, especially for existing Camel users. We should write clearly
somewhere this basic philosophy of keeping itself as a thin abstraction layer.
The existing basic concepts document doesn't seem to address it well:
https://camel.apache.org/camel-kafka-connector/latest/basic-concepts.html
2. Also we should address common questions from users, such as when CKC
cannot be the best solution, when we should get away from CKC and directly use
Camel Core, what my Camel application (architecture) would be like when we move
away from CKC, etc.
3. Talking about branding, perhaps **Camel** Kafka Connector might not be
the best name for the project, as it might give users a wrong expectation that
they could use the full power of Camel framework with it. Probably we should
stick to the abbreviation, CKC, as the primary name for the project, implying
it rather as the _Common_ Kafka Connectors, or the _Collection_ of Kafka
Connectors (like what [OKD](https://www.okd.io/) is trying to do). You could
still use _Powered by Apache Camel_ as the second punch-line or subtitle.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
