Hi Manas,
The approaches you described looks the same:
> each operator only stores what it needs.
> each downstream operator will "strip off" the config parameter that it
needs.
Can you please explain the difference?
Regards,
Roman
On Mon, May 11, 2020 at 8:07 AM Manas Kale <manaskal...@gmail.com> wrote:
> Hi,
> I have a single broadcast message that contains configuration data
> consumed by different operators. For eg:
> config = {
> "config1" : 1,
> "config2" : 2,
> "config3" : 3
> }
>
> Operator 1 will consume config1 only, operator 2 will consume config2 only
> etc.
>
>
> - Right now in my implementation the config message gets broadcast
> over operators 1,2,3 and each operator only stores what it needs.
>
>
> - A different approach would be to broadcast the config message to a
> single root operator. This will then enrich event data flowing through it
> with config1,config2 and config3 and each downstream operator will "strip
> off" the config parameter that it needs.
>
>
> *I was wondering which approach would be the best to go with performance
> wise. *I don't really have the time to implement both and compare, so
> perhaps someone here already knows if one approach is better or both
> provide similar performance.
>
> FWIW, the config stream is very sporadic compared to the event stream.
>
> Thank you,
> Manas Kale
>
>
>
>
