Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
pmscorca
Post Patron
Post Patron

Better Fabric architecture for critical real-time intelligence scenario

Hi,

I need to design a Fabric architecture for a critical real-time intelligence scenario, like f.e. an air traffic control context.

This architecture has to be as better as possible in terms of performance: the data must flow very very quickly from the source in order to produce any KPIs and insights in a report/dashboard (Power BI?), with a time within 2-3 seconds!

The input are represented by event messages with a size less 1 MB from an Azure Event hubs: it is possible to send more messages/second.

With these requirements it is crucial to choice the right architectural component, to set the related options and to apply the best practices.

Any helps to me in order to design the right real-time intelligence architecture for a critical scenario, please? Many thanks

1 ACCEPTED SOLUTION
datacoffee
Most Valuable Professional
Most Valuable Professional

Hello

With the use of Eventstream to listen to the Event Hub messages and the possibility to scale up the throughput directly from Fabric you should be able to get a really fast solution.

 

Schematic setup:

 

Event Hub --> |Fabric | --> Eventstream --> Eventhouse -->Real-Time Dashboard or KQL queryset --> Reflex item with alert

I've done this a lot of times and the "delay" here is around 500 ms (aprox 0.5 seconds)

 

All in all it depends on the setup, the use case and other requirements. Also the Fabric capacity must have enoug capacity units to use for compute and message handling. I don't know the amount of data in your setup, but I would start at F64 to see if that is enough.

 

Let me know if above works 🙂

View solution in original post

4 REPLIES 4
datacoffee
Most Valuable Professional
Most Valuable Professional

Hello

With the use of Eventstream to listen to the Event Hub messages and the possibility to scale up the throughput directly from Fabric you should be able to get a really fast solution.

 

Schematic setup:

 

Event Hub --> |Fabric | --> Eventstream --> Eventhouse -->Real-Time Dashboard or KQL queryset --> Reflex item with alert

I've done this a lot of times and the "delay" here is around 500 ms (aprox 0.5 seconds)

 

All in all it depends on the setup, the use case and other requirements. Also the Fabric capacity must have enoug capacity units to use for compute and message handling. I don't know the amount of data in your setup, but I would start at F64 to see if that is enough.

 

Let me know if above works 🙂

lbendlin
Super User
Super User

Our experience is that Kusto has about an 8 minute delay.

Hi,

many thanks for sharing your real experience.

If possible, could you indicate some details about the architecture applied, options and practices used, please? Thanks

Fabric Capacity Metrics App.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

Top Solution Authors
Top Kudoed Authors