<story><title>How and why the Relational Model works for databases</title><url>https://blog.the-pans.com/relational/</url></story><parent_chain></parent_chain><comment><author>brianmcc</author><text>The best advice I can give is that you can think of your app and its data store as either:&lt;p&gt;#1 code is of prime importance, data store is simply a &amp;quot;bucket&amp;quot; for its data&lt;p&gt;#2 data is of prime importance, code is simply the means to read&amp;#x2F;write&amp;#x2F;display it&lt;p&gt;In my personal experience, #2 is a way better way to work. Apps can come and go, but data can last a long time, and the better your database is modelled the better the outcomes you&amp;#x27;ll have long term.&lt;p&gt;Corollary - I have seen some abject disasters where #1 has been adopted. Not necessarily just because of #1 alone but it&amp;#x27;s certainly been a major factor.</text></comment>
<story><title>How and why the Relational Model works for databases</title><url>https://blog.the-pans.com/relational/</url></story><parent_chain></parent_chain><comment><author>caditinpiscinam</author><text>&amp;gt; All these database aspects remained virtually unchanged since 1970, which is absolutely remarkable. Thanks to the NoSQL movement, we know it&amp;#x27;s not because of a lack of trying.&lt;p&gt;Kind of an aside, but I find it odd that people treat &amp;quot;relational&amp;quot; and &amp;quot;SQL&amp;quot; as synonymous (as well as &amp;quot;non-relational&amp;quot; and &amp;quot;NoSQL&amp;quot;). You could make a relational database that was managed with a language other than SQL, right?</text></comment>