<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Redis on App Coding</title>
    <link>https://appcoding.com/tags/redis/</link>
    <description>Recent content in Redis on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/redis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Redis Semantics Without Redis: An Embedded State Engine for Counters, Leases and TTLs</title>
      <link>https://appcoding.com/redis-semantics-without-redis-an-embedded-state-engine-for-counters-leases-and-ttls/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/redis-semantics-without-redis-an-embedded-state-engine-for-counters-leases-and-ttls/</guid>
      <description>&lt;p&gt;A command-line tool should run only one copy of its nightly export at a time. A small web app wants to cap each user at 60 requests a minute. A desktop app needs to remember when it last synced. All three are state: an integer, a timestamp, an owner. All three usually get solved by adding Redis, because Redis has the verbs for them: &lt;code&gt;INCR&lt;/code&gt;, &lt;code&gt;SET NX PX&lt;/code&gt;, &lt;code&gt;EXPIRE&lt;/code&gt;. The app needed the verbs and got a server along with them, a port and a persistence config included.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
