Eventstream with multiple sources and multiple destinations

[frithjof_v]

Hi,

Should I use separate eventstreams (create another eventstream), or should I keep it inside one eventstream?

I want to map the source and destinations, as indicated by the yellow and purple lines. This seems to be not-so-straightforward in Eventstreams.

The main reason why I want to keep them in the same eventstream, is to save the "flat charge" cost of creating another eventstream:

Microsoft Fabric event streams capacity consumption - Microsoft Fabric | Microsoft Learn

Is there no out-of-the-box way to map a source to a destination?

Thanks!

[datacoffee · Accepted solution]

Hello

you could use one Eventstream and actually also one destination if you need it

then in the destination tabel you could build an Update Policy to load the different events to single tables.

This demands the source to keep the JSON objects "unfolded" and map the output to a single Dynamic data type in the destination table from the Eventstream.

cheers 😀

[Anonymous · Accepted solution]

Hi @datacoffee ,

Single Eventstream：Keeping everything in one eventstream can indeed save on the flat charge cost. You can map multiple sources to multiple destinations within a single eventstream. However, this might require more complex configurations and transformations to ensure data flows correctly between sources and destinations.

A single eventstream does not directly correspond to the source and destination one by one, you need to manually remove the unneeded columns.

Multiple Eventstreams: Creating separate eventstreams can simplify the mapping and management of sources to destinations. This approach can make your setup more modular and easier to troubleshoot. However, it will incur additional costs due to the flat charge for each eventstream.

Best Regards,

Neeko Tang

If this post  helps, then please consider Accept it as the solution  to help the other members find it more quickly. 

[datacoffee · Accepted solution]

Hello

you could use one Eventstream and actually also one destination if you need it

then in the destination tabel you could build an Update Policy to load the different events to single tables.

This demands the source to keep the JSON objects "unfolded" and map the output to a single Dynamic data type in the destination table from the Eventstream.

cheers 😀

[frithjof_v]

Thanks!

However I don't understand why it needs to be that complicated 😁

I would like to map sources and destinations inside the Eventstream.

cheers! 😊