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

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

Tzvia

Eventhouse Overview: Handling Real-Time Data with Microsoft Fabric

Today, Fabric introduces the Eventhouse (preview), a dynamic workspace hosting multiple KQL databases as part of Fabric Real-Time Analytics Overview of Real-Time Analytics - Microsoft Fabric | Microsoft Learn

Handling Real-Time Data with Microsoft Fabric

Eventhouses assume a pivotal role in the Microsoft Fabric ecosystem by offering a robust solution for managing and analyzing substantial volumes of real-time data. Eventhouses efficiently handling real-time data streams, empower organizations to ingest, process, and analyze data nearly in real-time. The scalability of Eventhouses ensures optimal performance and resource utilization, making them particularly valuable in scenarios where timely insights are imperative. Ideal for scenarios involving event-based data such as telemetry and log data, time series and IoT data, security and compliance logs, or financial records.

Eventhouse_Overview_Handling_Real-Time_Data_with_Microsoft_FabricEventhouse_Overview_Handling_Real-Time_Data_with_Microsoft_Fabric

Key Features of Eventhouses:

1. Workspace of Databases:

  • An Eventhouse is essentially a shared workspace for databases, facilitating efficient management across specific projects.
  • Simultaneous management of multiple databases optimizes performance and reduces costs.
  • Unified monitoring and management are available across all databases and on a per-database basis.

Eventhouse_Overview_Handling_Real-Time_Data_with_Microsoft_FabricEventhouse_Overview_Handling_Real-Time_Data_with_Microsoft_Fabric

2. Tailored to Time-Based, Streaming Events:

  • Specifically designed for time-based, streaming events supporting various data formats.
  • Ingest data from diverse sources and pipelines like Eventstream, SDKs, Kafka, Logstash, and more.
  • Automatic indexing and partitioning based on ingestion time.

3. Minimum Consumption:

  • Optimizes cost by allowing the suspension of the service when not in use.
  • Minimum consumption ensures the service is always available at a selected minimum level, minimizing latency upon reactivation.
  • Applicable for time-sensitive systems intolerant to latency.

Next Steps:

  1. Read More: Eventhouse overview (preview) - Microsoft Fabric | Microsoft Learn
  2. How to select Data Store in Microsoft Fabric - Fabric decision guide - choose a data store - Microsoft Fabric | Microsoft Learn
  3. The next logical step is to create your own Eventhouse, leveraging the power of Eventhouses in Preview - Create an Eventhouse (preview) - Microsoft Fabric | Microsoft Learn