<?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 Unifying streaming and batch pipeline stacks in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/unifying-streaming-and-batch-pipeline-stacks/m-p/35783#M5155</link>
    <description>&lt;P&gt;At my company we have disjointed data stores for real-time ML inference vs. batch training/inference, causing user pain points when searching for features in different feature stores. I am excited to use Delta Lake and the Streaming Infrasturcture to make data more discoverable/usable for our ML use cases.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jun 2023 19:30:44 GMT</pubDate>
    <dc:creator>Lexisquid</dc:creator>
    <dc:date>2023-06-28T19:30:44Z</dc:date>
    <item>
      <title>Unifying streaming and batch pipeline stacks</title>
      <link>https://community.databricks.com/t5/get-started-discussions/unifying-streaming-and-batch-pipeline-stacks/m-p/35783#M5155</link>
      <description>&lt;P&gt;At my company we have disjointed data stores for real-time ML inference vs. batch training/inference, causing user pain points when searching for features in different feature stores. I am excited to use Delta Lake and the Streaming Infrasturcture to make data more discoverable/usable for our ML use cases.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 19:30:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/unifying-streaming-and-batch-pipeline-stacks/m-p/35783#M5155</guid>
      <dc:creator>Lexisquid</dc:creator>
      <dc:date>2023-06-28T19:30:44Z</dc:date>
    </item>
  </channel>
</rss>

