<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Providers on Dapr Docs</title><link>https://docs.dapr.io/developing-ai/dapr-agents/integrations/providers/</link><description>Recent content in Providers on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.dapr.io/developing-ai/dapr-agents/integrations/providers/index.xml" rel="self" type="application/rss+xml"/><item><title>Drasi</title><link>https://docs.dapr.io/developing-ai/dapr-agents/integrations/providers/drasi/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.dapr.io/developing-ai/dapr-agents/integrations/providers/drasi/</guid><description>&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note&lt;/h4>

 This integration is currently in Alpha; breaking changes may occur at any time.

&lt;/div>

&lt;p>The Drasi extension in Dapr Agents enables &lt;code>DurableAgent&lt;/code> runs to be triggered by Drasi events.&lt;/p>
&lt;h2 id="why-use-drasi">Why Use Drasi?&lt;/h2>
&lt;p>Many systems need to react to changes produced by other systems in near real-time. Traditional polling cannot detect the absence of change, or changes that occur at an extremely high frequency without unnecessary load on source systems (even without considering network delay). Raw changes are usually not actionable, requiring custom change data capture (CDC) pipelines to process changes at scale and convert them into meaningful domain events. However, these pipelines can be expensive (if managed) or difficult to set up and maintain (if self-hosted).&lt;/p></description></item></channel></rss>