<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migrations on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/migrations/</link><description>Recent content in Migrations on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 08 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/migrations/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 4: Data Persistence: PostgreSQL Integration &amp;amp; Migrations</title><link>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/04-postgresql-integration/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/04-postgresql-integration/</guid><description>&lt;h2 id="chapter-4-data-persistence-postgresql-integration--migrations"&gt;Chapter 4: Data Persistence: PostgreSQL Integration &amp;amp; Migrations&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 4 of our Node.js backend project series! So far, we&amp;rsquo;ve established a robust project structure, set up our Fastify server, and implemented essential middleware for request handling and error management. While our API can process requests, it currently lacks the ability to store and retrieve data persistently. This severely limits its utility, as any information processed is lost once the server restarts.&lt;/p&gt;</description></item></channel></rss>