Hi,

Any reply on our last comment?

 

Yuval Alon

amdocs technology – Digital

Mobile: +972-52-6148937

Office:   +972-9-7789641

email:   yuvalal@amdocs.com

amdocs-a

 

From: Assaf Katz
Sent: Wednesday, November 29, 2017 6:51 PM
To: users@kafka.apache.org
Cc: Zeevik Liak <Zeevik.Liak@amdocs.com>; Yuval Alon <YUVALAL@Amdocs.com>
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:wim.vanleuven@highestpoint.biz]
Sent: Wednesday, 29 November 2017 18:47
To: users@kafka.apache.org
Cc: Assaf Katz <assaf.katz@amdocs.com>; Zeevik Liak <Zeevik.Liak@amdocs.com>
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 <YUVALAL@amdocs.com> 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
Office:   +972-9-7789641
email:   yuvalal@amdocs.com<mailto:yuvalal@amdocs.com>

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