If you haven’t built in logic from the start (with micro-service version 1) then I think you’ll need some sort of “router” in the middle that knows the routing logic.
-Dave From: Assaf Katz [mailto:[email protected]] Sent: Wednesday, December 13, 2017 3:12 AM To: Yuval Alon <[email protected]>; [email protected] Cc: Zeevik Liak <[email protected]> Subject: RE: Kafka & Canary Release No From: Yuval Alon Sent: Wednesday, 13 December 2017 10:52 To: [email protected]<mailto:[email protected]> Cc: Zeevik Liak <[email protected]<mailto:[email protected]>>; Assaf Katz <[email protected]<mailto:[email protected]>> Subject: RE: Kafka & Canary Release Hi, Any reply on our last comment? Yuval Alon amdocs technology – Digital Mobile: +972-52-6148937 Office: +972-9-7789641 email: [email protected]<mailto:[email protected]> [amdocs-a] From: Assaf Katz Sent: Wednesday, November 29, 2017 6:51 PM To: [email protected]<mailto:[email protected]> Cc: Zeevik Liak <[email protected]<mailto:[email protected]>>; Yuval Alon <[email protected]<mailto:[email protected]>> Subject: RE: Kafka & Canary Release Hi, It doesn’t so simple only micro service 1 knows about it - if micro service 2 send to micro service 1, it doesn’t have any idea that micro service 1 was updated. So we need to route it on message hub - Kafka. Thanks, Assaf From: Wim Van Leuven [mailto:[email protected]] Sent: Wednesday, 29 November 2017 18:47 To: [email protected]<mailto:[email protected]> Cc: Assaf Katz <[email protected]<mailto:[email protected]>>; Zeevik Liak <[email protected]<mailto:[email protected]>> Subject: Re: Kafka & Canary Release Isn't that simply a matter of changing your key to route the element to the right topic for 1 or the other microservice? -w On Wed, 29 Nov 2017 at 17:09 Yuval Alon <[email protected]<mailto:[email protected]>> wrote: Hello, We are using Apache Kafka 0.10.2, which we understand is not supporting “Canary Release<https://martinfowler.com/bliki/CanaryRelease.html>” Is it in your pipeline, if so, when it’s going to be released? Explanation of the issue: We hold two different versions of micro services that subscribes to the same topic. We would like to get only message that match some condition to each of them, for example: 1. Message with user=foo to micro service instance of version 1 2. Message with user<>foo to micro service instance of version 2 The problem is how to route to right instances? Yuval Alon amdocs technology – Digital Mobile: +972-52-6148937<tel:+972%2052-614-8937> Office: +972-9-7789641<tel:+972%209-778-9641> email: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This e-mail and any files transmitted with it are confidential, may contain sensitive information, and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender by reply e-mail immediately and destroy all copies of the e-mail and any attachments.
