<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Real time Streaming to AI Engine  at Databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/real-time-streaming-to-ai-engine-at-databricks/m-p/175299#M56979</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;Usercase: Fraud Detection&amp;nbsp;&lt;/P&gt;&lt;P&gt;Technology : Databricks, Kafka, Microsoft Foundry, Dashboard showing real-time reports&lt;/P&gt;&lt;P&gt;Ask: Please let me know if any reference or technology details to achieve 1-2 milli second (Max) latency using above technology stack.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;</description>
    <pubDate>Mon, 02 Nov 2026 06:26:26 GMT</pubDate>
    <dc:creator>abhietc31</dc:creator>
    <dc:date>2026-11-02T06:26:26Z</dc:date>
    <item>
      <title>Real time Streaming to AI Engine  at Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/real-time-streaming-to-ai-engine-at-databricks/m-p/175299#M56979</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;Usercase: Fraud Detection&amp;nbsp;&lt;/P&gt;&lt;P&gt;Technology : Databricks, Kafka, Microsoft Foundry, Dashboard showing real-time reports&lt;/P&gt;&lt;P&gt;Ask: Please let me know if any reference or technology details to achieve 1-2 milli second (Max) latency using above technology stack.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2026 06:26:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/real-time-streaming-to-ai-engine-at-databricks/m-p/175299#M56979</guid>
      <dc:creator>abhietc31</dc:creator>
      <dc:date>2026-11-02T06:26:26Z</dc:date>
    </item>
    <item>
      <title>Re: Real time Streaming to AI Engine  at Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/real-time-streaming-to-ai-engine-at-databricks/m-p/175322#M56983</link>
      <description>&lt;P&gt;One thing worth pinning down first is where the 1-2 ms is measured. If it is the whole path from the transaction event to a fraud score back to the payment service, that budget is tighter than a Kafka hop plus a network round trip to a hosted model endpoint, because the round trip alone tends to eat it. If it is only the streaming leg (Kafka in, a feature or rule step, Kafka out), that is a different conversation.&lt;/P&gt;&lt;P&gt;On the Databricks side, the closest thing to what you describe is real-time mode in Structured Streaming. The docs show sample end-to-end p99 around 4 to 5 ms for simple pipelines reading and writing Kafka, and they say themselves that the number depends on your business logic and has to be measured with it. It needs a dedicated classic cluster on a recent runtime with the config flag turned on, it was public preview per the docs, and foreachBatch is not supported. So even the good case is a few ms, not 1-2.&lt;/P&gt;&lt;P&gt;If 1-2 ms is a hard requirement at the decision point, the usual pattern is to keep scoring inside or right next to the transaction service (small model or rules held in memory, features cached) and use Databricks for training, feature computation, backtesting and the near-real-time dashboard. I would benchmark with your real payload and a p99 target before committing. The e2eLatencyMs metric in the streaming progress is a decent first measurement.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2026 12:57:40 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/real-time-streaming-to-ai-engine-at-databricks/m-p/175322#M56983</guid>
      <dc:creator>DoTA</dc:creator>
      <dc:date>2026-11-02T12:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: Real time Streaming to AI Engine  at Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/real-time-streaming-to-ai-engine-at-databricks/m-p/175330#M56987</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/269107"&gt;@abhietc31&lt;/a&gt;&amp;nbsp;I assume this is what you are looking for :&lt;BR /&gt;&lt;A href="https://docs.databricks.com/aws/en/structured-streaming/real-time/concepts" target="_blank"&gt;https://docs.databricks.com/aws/en/structured-streaming/real-time/concepts&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Possible in both pyspark structured streaming pipelines or lakeflow pipelines. Depends how you are curating your pipelines.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Real-time mode (RTM) is a trigger type for &lt;/SPAN&gt;&lt;SPAN&gt;Structured Streaming&lt;/SPAN&gt;&lt;SPAN&gt; that is up to 100x faster than micro-batch mode. Use RTM for operational workloads that require immediate response to streaming data, such as fraud detection and real-time personalization.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;e.g.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;query = (&lt;BR /&gt;spark.readStream&lt;BR /&gt;.format("kafka")&lt;BR /&gt;.option("kafka.bootstrap.servers", broker_address)&lt;BR /&gt;.option("startingOffsets", "earliest")&lt;BR /&gt;.option("subscribe", input_topic)&lt;BR /&gt;.load()&lt;BR /&gt;.writeStream&lt;BR /&gt;.format("kafka")&lt;BR /&gt;.option("kafka.bootstrap.servers", broker_address)&lt;BR /&gt;.option("topic", output_topic)&lt;BR /&gt;.option("checkpointLocation", checkpoint_location)&lt;BR /&gt;.trigger(realTime="5 minutes")&lt;BR /&gt;.outputMode("update")&lt;BR /&gt;.start()&lt;BR /&gt;)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2026 14:25:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/real-time-streaming-to-ai-engine-at-databricks/m-p/175330#M56987</guid>
      <dc:creator>saurabh18cs</dc:creator>
      <dc:date>2026-11-02T14:25:23Z</dc:date>
    </item>
  </channel>
</rss>

