<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Relational Model on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/relational-model/</link><description>Recent content in Relational Model on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 17 Apr 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/relational-model/index.xml" rel="self" type="application/rss+xml"/><item><title>Databases (1): Data Models and SQL — Why Tables Won (For Now)</title><link>https://www.chenk.top/en/databases/01-data-models-and-sql/</link><pubDate>Wed, 17 Apr 2024 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/databases/01-data-models-and-sql/</guid><description>&lt;p>Every application you have ever used sits on top of a data model. Pick the wrong one and you spend the next three years fighting your own database instead of shipping features.&lt;/p>
&lt;p>For the past four decades, one model has dominated: the relational model. Flat tables, foreign keys, SQL. It is not glamorous. It is not trendy. But there is a reason almost every bank, airline, hospital, and e-commerce platform still runs on it — and understanding &lt;em>why&lt;/em> is the first step to understanding databases at all.&lt;/p></description></item></channel></rss>