<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MySQL on Ken Huang</title>
    <link>https://blog.kenhuang.io/tags/mysql/</link>
    <description>Recent content in MySQL on Ken Huang</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>whatacold@gmail.com (Ken Huang)</managingEditor>
    <webMaster>whatacold@gmail.com (Ken Huang)</webMaster>
    <lastBuildDate>Thu, 25 Jun 2020 22:37:00 +0800</lastBuildDate>
    <atom:link href="https://blog.kenhuang.io/tags/mysql/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Is It Safe to Use Redis As a Data Store?</title>
      <link>https://blog.kenhuang.io/blog/2020-06-25-is-it-safe-to-use-redis-as-a-data-store/</link>
      <pubDate>Thu, 25 Jun 2020 22:37:00 +0800</pubDate><author>whatacold@gmail.com (Ken Huang)</author>
      <guid>https://blog.kenhuang.io/blog/2020-06-25-is-it-safe-to-use-redis-as-a-data-store/</guid>
      <description>&lt;p&gt;&#xA;Traditionally we are used to storing data in an RDBMS like MySQL, and avoid using in-memory solutions such as Redis, to have a confidence of no data loss. Sometimes I find that we are so stubborn with MySQL that ending up with a complicated design, and I&amp;#39;ve even seen a solution that stores data in MySQL and then using Redis as a cache for it to improve read performance in the meanwhile. And to make the data in the cache as consistent as possible with the data in MySQL, it introduces other mechanisms, but the result is still not 100% consistent.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
