<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Backend on David Lang</title>
    <link>https://www.davidlang.tech/tags/backend/</link>
    <description>Recent content in Backend on David Lang</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 10 Aug 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.davidlang.tech/tags/backend/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL vs MySQL: Choosing the Right Database</title>
      <link>https://www.davidlang.tech/posts/postgresql-vs-mysql-choosing-the-right-database/</link>
      <pubDate>Mon, 10 Aug 2020 00:00:00 +0000</pubDate>
      <guid>https://www.davidlang.tech/posts/postgresql-vs-mysql-choosing-the-right-database/</guid>
      <description>&lt;p&gt;Relational databases remain the backbone of most full stack applications. PostgreSQL and MySQL are the two most common choices-each excels in different scenarios.&lt;/p&gt;&#xA;&lt;h2 id=&#34;postgresql-strengths&#34;&gt;PostgreSQL Strengths&lt;/h2&gt;&#xA;&lt;p&gt;PostgreSQL offers advanced types (JSONB, arrays), full-text search, robust concurrency (MVCC), and extensions like PostGIS. It is the default choice for complex queries, analytics-heavy apps, and strict data integrity.&lt;/p&gt;&#xA;&lt;h2 id=&#34;mysql-strengths&#34;&gt;MySQL Strengths&lt;/h2&gt;&#xA;&lt;p&gt;MySQL (and MariaDB) are widely hosted, familiar to many teams, and perform well for read-heavy web workloads. Managed offerings are plentiful and often slightly cheaper at small scale.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building REST APIs with Node.js and Express</title>
      <link>https://www.davidlang.tech/posts/building-rest-apis-with-nodejs-and-express/</link>
      <pubDate>Sun, 22 Mar 2020 00:00:00 +0000</pubDate>
      <guid>https://www.davidlang.tech/posts/building-rest-apis-with-nodejs-and-express/</guid>
      <description>&lt;p&gt;Express remains the most popular framework for building REST APIs in Node.js. It is minimal, unopinionated, and pairs well with middleware for auth, validation, and logging.&lt;/p&gt;&#xA;&lt;h2 id=&#34;project-setup&#34;&gt;Project Setup&lt;/h2&gt;&#xA;&lt;p&gt;Initialize a project and install Express:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;npm init -y&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;npm install express&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Create a basic server with JSON body parsing:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-javascript&#34; data-lang=&#34;javascript&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#268bd2&#34;&gt;const&lt;/span&gt; express &lt;span style=&#34;color:#719e07&#34;&gt;=&lt;/span&gt; require(&lt;span style=&#34;color:#2aa198&#34;&gt;&amp;#39;express&amp;#39;&lt;/span&gt;);&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#268bd2&#34;&gt;const&lt;/span&gt; app &lt;span style=&#34;color:#719e07&#34;&gt;=&lt;/span&gt; express();&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;app.use(express.json());&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#268bd2&#34;&gt;const&lt;/span&gt; items &lt;span style=&#34;color:#719e07&#34;&gt;=&lt;/span&gt; [];&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;app.get(&lt;span style=&#34;color:#2aa198&#34;&gt;&amp;#39;/api/items&amp;#39;&lt;/span&gt;, (req, res) =&amp;gt; res.json(items));&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;app.post(&lt;span style=&#34;color:#2aa198&#34;&gt;&amp;#39;/api/items&amp;#39;&lt;/span&gt;, (req, res) =&amp;gt; {&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#268bd2&#34;&gt;const&lt;/span&gt; item &lt;span style=&#34;color:#719e07&#34;&gt;=&lt;/span&gt; { id&lt;span style=&#34;color:#719e07&#34;&gt;:&lt;/span&gt; &lt;span style=&#34;color:#b58900&#34;&gt;Date&lt;/span&gt;.now(), ...req.body };&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  items.push(item);&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  res.status(&lt;span style=&#34;color:#2aa198&#34;&gt;201&lt;/span&gt;).json(item);&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;});&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;app.listen(&lt;span style=&#34;color:#2aa198&#34;&gt;3000&lt;/span&gt;, () =&amp;gt; console.log(&lt;span style=&#34;color:#2aa198&#34;&gt;&amp;#39;API running on :3000&amp;#39;&lt;/span&gt;));&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id=&#34;structure-for-production&#34;&gt;Structure for Production&lt;/h2&gt;&#xA;&lt;p&gt;Organize routes by resource (&lt;code&gt;/users&lt;/code&gt;, &lt;code&gt;/orders&lt;/code&gt;), use a router per domain, and separate controllers from route definitions. Add &lt;code&gt;helmet&lt;/code&gt; for security headers, &lt;code&gt;cors&lt;/code&gt; for cross-origin access, and a centralized error handler that returns consistent JSON error shapes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
