<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Python-based RedisGears recipes on Docs</title>
    <link>https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/recipes/</link>
    <description>Recent content in Python-based RedisGears recipes on Docs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/recipes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Write-behind caching</title>
      <link>https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/recipes/write-behind/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/python/recipes/write-behind/</guid>
      <description>&lt;p&gt;Write-behind is a caching strategy in which the cache layer itself connects to the backing database. This means that your applications need only ever connect to your cache layer, and the cache then reads from or updates the backing database as needed. Redis currently supports write-behind caching in &lt;a href=&#34;https://redis.io/docs/latest/operate/rs/&#34;&gt;Redis Software&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Here&#39;s how these caching patterns work:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Your application uses the cache for reads and writes.&lt;/li&gt;&#xA;&lt;li&gt;The cache syncs any changed data to the backing database asynchronously.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;!-- ### Read-through caching&#xA;&#xA;1. Your application reads from the cache. If there&#39;s a cache hit, the data is returned.&#xA;1. If there&#39;s cache miss, the cache retrieves the data from your backing database (think Oracle, PostgreSQL, etc.). The data is then stored in the cache and returned. --&gt;&#xA;&lt;h2 id=&#34;install-the-write-behind-recipe&#34; class=&#34;group relative&#34;&gt;&#xA;  Install the write-behind recipe&#xA;  &lt;a href=&#34;#install-the-write-behind-recipe&#34; class=&#34;header-link opacity-0 group-hover:opacity-100 transition-opacity duration-200 ml-1 align-baseline&#34; aria-label=&#34;Link to this section&#34; title=&#34;Copy link to clipboard&#34;&gt;&#xA;    &lt;svg class=&#34;inline-block w-4 h-4 align-baseline&#34; fill=&#34;currentColor&#34; viewBox=&#34;0 0 20 20&#34; xmlns=&#34;http://www.w3.org/2000/svg&#34;&gt;&#xA;      &lt;path fill-rule=&#34;evenodd&#34; d=&#34;M12.586 4.586a2 2 0 112.828 2.828l-3 3a2 2 0 01-2.828 0 1 1 0 00-1.414 1.414 4 4 0 005.656 0l3-3a4 4 0 00-5.656-5.656l-1.5 1.5a1 1 0 101.414 1.414l1.5-1.5zm-5 5a2 2 0 012.828 0 1 1 0 101.414-1.414 4 4 0 00-5.656 0l-3 3a4 4 0 105.656 5.656l1.5-1.5a1 1 0 10-1.414-1.414l-1.5 1.5a2 2 0 11-2.828-2.828l3-3z&#34; clip-rule=&#34;evenodd&#34;&gt;&lt;/path&gt;&#xA;    &lt;/svg&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;The write-behind recipe comes with two types of dependencies:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
