Can we happy-hack a sidecar concept? #24
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Docker Compose aside ...
Maybe Knative will beat us to the Kafka sidecar pattern :) but development today with countless restarts of a service that needed to warm up a kafka connection only for simple table-topic lookups got me thinking about the advantages with a kafka-cache sidecar.
Also integration testing required kafka while all I'd actually want was to pre-load some key-value pairs. Maybe something like https://www.npmjs.com/package/jsondown could provide that. The sidecar pattern would make kafka-cache and a stub interchangeable at runtime.
While I was in this mood I also had crazy ideas about using annotations to declare what topics and/or types to produce and/or consume, as solution to Yolean/kubernetes-kafka#101. Maybe CloudEvents will beat us to that :)