Fabric-Rti-101

Fabric RTI 101: Edge Scenarios

Fabric RTI 101: Edge Scenarios

Edge computing plays a key role in modern real-time data architectures by moving some processing closer to where data is generated. Instead of sending every raw data point to the cloud, devices or gateways at the edge can handle local filtering, aggregation, and enrichment.

Edge Scenarios

Using Azure IoT Edge or similar frameworks, organizations can deploy lightweight processing modules directly on devices, gateways, or factory controllers. These modules can execute logic such as:

2026-10-28

Fabric RTI 101: Digital Twins

Fabric RTI 101: Digital Twins

A digital twin is a virtual representation of a physical system or asset - such as an engine, a building, a production line, or a logistics network.

Unlike a static model, a digital twin is continuously synchronized with its real-world counterpart through real-time telemetry and sensor data. This constant data flow ensures that the virtual model reflects the current operating state of the physical system.

Digital Twins

The purpose of a digital twin extends beyond visualization. It enables simulation, monitoring, and predictive analysis. For example, engineers can test what-if scenarios - such as how a machine might behave under higher load or different environmental conditions - without interrupting operations. It also supports predictive maintenance, by identifying early indicators of wear or failure before they result in downtime.

2026-10-26

Fabric RTI 101: Emerging Patterns for Real-Time

Fabric RTI 101: Emerging Patterns for Real-Time

Several important trends are shaping the future of real-time data systems, moving beyond simple event streaming toward intelligent, autonomous, and action-oriented pipelines.

One key direction is the integration of streaming with AI and machine learning. Instead of passively analyzing data, systems can now make inferences or decisions as events occur - for example, predicting failures, recommending actions, or adapting system behavior in real time. This shift from descriptive to predictive and prescriptive analytics marks an important evolution.

2026-10-24

Fabric RTI 101: Integrating RTI vs Azure Stream Analytics

Fabric RTI 101: Integrating RTI vs Azure Stream Analytics

Both Fabric Real-Time Intelligence (RTI) and Azure Stream Analytics (ASA) are designed to process streaming data, but they serve different roles within the Microsoft data ecosystem.

Integrating RTI vs Azure Stream Analytics

Fabric RTI is part of the broader Microsoft Fabric platform. It uses KQL (Kusto Query Language) as its foundation and is tightly integrated with OneLake, Power BI, and other Fabric components such as Eventstream and Activator. This integration makes it suitable for end-to-end real-time analytics, where streaming data is combined with historical data, transformed, visualized, and acted upon - all within one environment.

2026-10-22

Fabric RTI 101: Integrating KQL Follower Databases

Fabric RTI 101: Integrating KQL Follower Databases

A KQL Follower Database provides a way to share data across clusters or organizations while maintaining control and performance. Instead of duplicating ingestion pipelines or exporting data manually, a follower database automatically mirrors data from a leader database hosted in another KQL cluster.

Integrating KQL Follower Databases

This pattern is especially useful when multiple teams, regions, or tenants need access to the same data for analytics.

The follower maintains a read-only, synchronized view of the source. Updates to the leader are automatically reflected in the follower without any manual refresh or re-ingestion.

2026-10-20

Fabric RTI 101: Integrating with MQTT

Fabric RTI 101: Integrating with MQTT

MQTT is a lightweight messaging protocol designed for IoT and edge environments.

It uses a publish/subscribe model, making it efficient for devices that send small amounts of data over unreliable or bandwidth-limited connections - such as sensors, embedded devices, or mobile units.

Integrating with MQTT

In MQTT, a central broker (like Eclipse Mosquitto, HiveMQ, or EMQX) handles communication between clients. Devices publish messages to topics, and subscribers receive updates for the topics they’re interested in. This model decouples producers and consumers, improving scalability and resilience.

2026-10-18

Fabric RTI 101: Integrating with Google Cloud Pub-Sub

Fabric RTI 101: Integrating with Google Cloud Pub-Sub

Google Cloud Pub/Sub is a fully managed event ingestion and messaging system.

It supports large-scale, asynchronous communication between services. It is widely used for event-driven architectures, analytics pipelines, and IoT telemetry.

Integrating with Google Cloud Pub-Sub

In this integration model, Pub/Sub acts as a cross-cloud source for Fabric. Messages published to topics in Google Cloud - such as application logs, telemetry events, or transaction data - can be exported or streamed into Fabric Eventstream for analysis.

2026-10-16

Fabric RTI 101: Integrating with Spark Structured Streaming

Fabric RTI 101: Integrating with Spark Structured Streaming

Spark Structured Streaming is part of Apache Spark’s ecosystem and is designed for continuous processing of data streams using a micro-batch model. Unlike true event-by-event streaming engines, Spark processes data in very small, frequent batches - giving it a balance between throughput and fault tolerance.

Integrating with Spark Structured Streaming

This approach makes Spark Structured Streaming especially effective for large-scale ETL and data transformation workloads. It can ingest data from a variety of real-time sources, perform complex operations such as joins, windowed aggregations, or enrichment, and then write the results to multiple destinations.

2026-10-14

Fabric RTI 101: Integrating with Flink

Fabric RTI 101: Integrating with Flink

Apache Flink is a distributed stream processing framework designed for real-time analytics and event-driven applications. It’s well known for its ability to handle large volumes of continuous data with stateful computation, meaning it can maintain context across many events - something that simpler streaming systems struggle with.

Integrating with Flink

A key strength of Flink is its support for Complex Event Processing (CEP).

CEP allows you to define and detect patterns of events rather than just single occurrences. For example, you could detect a sequence such as three failed login attempts followed by a successful one, or identify correlated sensor readings that indicate a developing fault.

2026-10-12

Fabric RTI 101: Integrating with Kafka Streams

Fabric RTI 101: Integrating with Kafka Streams

Kafka Streams is a client-side stream processing library that operates directly on Kafka topics. Unlike a separate processing engine, it runs within your own application or service, allowing data transformation to occur close to where the events are produced.

Integrating with Kafka Streams

This makes it ideal for preprocessing data before it reaches Fabric. You can use Kafka Streams to perform tasks such as data enrichment, filtering, or lightweight aggregation. For instance, before sending events to Fabric, you might:

2026-10-10