You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/12/08 17:41:33 UTC

[GitHub] [camel-k] lburgazzoli edited a comment on issue #2585: Add the option to inject the integration container as a side car to another deployment

lburgazzoli edited a comment on issue #2585:
URL: https://github.com/apache/camel-k/issues/2585#issuecomment-989029797


   I guess here the main use case it to have something that is similar to [dapr](https://dapr.io/) where as example, the right integration is injected depending on an environment, abstracting the business logic from the platform so, on azure you may inject an Azure specific wrapper for their pub/sub buts, whereas on GCP you may want to inject a goggle specific one but for the business logic POV, it is always a RPC (REST, gRPC) call to a sidecar.
   
   I find the pattern very interesting and it is something we were looking at in the past.


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org