<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sessions on KvSQL.com</title>
    <link>https://kvsql.com/tags/sessions/</link>
    <description>Recent content in Sessions on KvSQL.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://kvsql.com/tags/sessions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Case Study: Sessions and Reporting in One Store Instead of Two</title>
      <link>https://kvsql.com/case-study-sessions-and-reporting-in-one-store-instead-of-two/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://kvsql.com/case-study-sessions-and-reporting-in-one-store-instead-of-two/</guid>
      <description>&lt;p&gt;A web application checks its session table on every request. A token comes in, and the app needs the user behind it, fast. Once in a while somebody wants a different view of the same data: how many sessions are live per country, or every session of one user, revoked at once when a password changes. Teams often split this in two, with sessions in Redis for speed and a copy in SQL for the reports and the bulk revokes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
