squakez commented on issue #3003: URL: https://github.com/apache/camel-k/issues/3003#issuecomment-1040004983
> @squakez One further question from an architecture point of view. > > If an Integration Kit is being used by multiple Integrations, the Integration itself isn't self contained; as it has dependencies to an Integration Kit. The relation between Integration Kits and Integrations is 1:n, what I got from your answers. > > How does this fit into a micro service pattern? As I understand the micro service approach such a micro service should be autonomous. The first autonomous layer with Camel-K are multiple integrations dependent to one Integration Kit. > > What are the reasons behind this? How could be reached an autonomy of single Integrations? Sharing a base layer is a tradeoff required to improve the speed for build/execution and to reduce the resource needed to store the images. I don't think it affect the autonomy of the microservice, given that the Kit is **immutable**. Also, when working with containers you always use some layer built in top of another. This is exactly the same concept. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
