A facilities team wants building-management fire-suppression-system heartbeat events routed continuously to both an Eventhouse for historical KQL analysis and a Data Activator that pages on-call staff if a heartbeat is missing for more than two minutes, with light field renaming along the way and no team member available who can write Spark code. Which Fabric engine should this team choose?
Select an answer to reveal the explanation.
Short Explanation
Powerful isn't the same as right for the job — the team here needs routing and light renaming with no code, to two destinations at once. An Eventstream does exactly that out of the box, no Spark expertise required.
Full Explanation
An Eventstream is the no-code Fabric engine for continuous stream processing: it ingests a live source, applies lightweight operations such as field renaming, and fans the result out to multiple destinations at once, including both an Eventhouse and a Data Activator, without requiring anyone on the team to write code. That combination — no-code requirement, light transformation, and simultaneous multi-destination routing — maps directly onto what Eventstream is built for.
A Spark structured streaming notebook, despite being the more powerful and flexible option in the abstract, requires PySpark expertise the team explicitly does not have, making it the wrong practical choice even though it is technically capable of the same routing. A Dataflow Gen2 is a batch-oriented transform-and-load tool; it is not designed to continuously watch a live heartbeat stream and immediately notify a Data Activator the moment an anomaly occurs, which this fire-suppression monitoring scenario requires. A T-SQL scheduled job querying a Warehouse every two minutes only reacts on a fixed polling interval against data that has already landed, introducing exactly the kind of latency a missing-heartbeat safety alert cannot tolerate, and it also has no native path to page an on-call Data Activator.
A caveat: monitoring that later needs custom stateful logic beyond routing and renaming would require Spark skill the team would need to build or bring in, since Eventstream's canvas is limited to its built-in operations. Operationally, verify the choice by confirming a deliberately paused heartbeat stream causes the Data Activator to page within the two-minute threshold while historical heartbeats still land correctly in the Eventhouse.