<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Golang on Aditya Naik | Personal Website</title>
    <link>https://d6cbd428.hugo-blog-e6x.pages.dev/tags/golang/</link>
    <description>Recent content in Golang on Aditya Naik | Personal Website</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 16 Jul 2023 08:56:12 +0000</lastBuildDate>
    <atom:link href="https://d6cbd428.hugo-blog-e6x.pages.dev/tags/golang/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Redis | Cache user data with Redis in golang app</title>
      <link>https://d6cbd428.hugo-blog-e6x.pages.dev/blog/2023/07/16/redis-cache-user-data-with-redis-in-golang-app/</link>
      <pubDate>Sun, 16 Jul 2023 08:56:12 +0000</pubDate>
      <guid>https://d6cbd428.hugo-blog-e6x.pages.dev/blog/2023/07/16/redis-cache-user-data-with-redis-in-golang-app/</guid>
      <description>&lt;p&gt;Imagine this. Your fantastic app, written in Golang, is chugging along. You are getting more users and increased activity all the time. Over time, you start hearing complaints about slow performance. This takes you by surprise, and you start exploring potential causes for the slowdown.&lt;/p&gt;&#xA;&lt;p&gt;The absolute obvious problem you want to fix first is the user behavior tracking system. You want to know most frequently used paths to select code areas for refactoring, simplification, optimization and potential automation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
