<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Nosql on Duc Truong</title>
    <link>https://ductruong.com/en/tags/nosql/</link>
    <description>Recent content in Nosql on Duc Truong</description>
    <generator>Hugo -- 0.144.2</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Aug 2024 19:36:17 +0700</lastBuildDate>
    <atom:link href="https://ductruong.com/en/tags/nosql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Database: Why did NoSQL emerge when SQL already existed?</title>
      <link>https://ductruong.com/en/blog/2024/08/database-why-did-nosql-emerge-when-sql-already-existed/</link>
      <pubDate>Sat, 10 Aug 2024 19:36:17 +0700</pubDate>
      <guid>https://ductruong.com/en/blog/2024/08/database-why-did-nosql-emerge-when-sql-already-existed/</guid>
      <description>&lt;p&gt;Recently, I had the opportunity to participate in the development and construction of a large-scale product, designed to serve hundreds of
thousands, even millions, of users daily. As a result, the core architecture was built on the CQRS Pattern, a model that separates data
reading and writing operations. This approach has allowed us to optimize the system’s performance and scalability while minimizing risks
when handling large volumes of data. Through these experiences, I’ve been able to answer a question that has puzzled me for a long time:
&amp;lsquo;Why did NoSQL emerge when SQL already existed?&amp;rsquo; In this article, I’ll share with you the origins and development reasons behind SQL and
NoSQL, as well as the challenges each of these database systems faces. Let’s dive in!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
