<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Persistence on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/data-persistence/</link><description>Recent content in Data Persistence on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/data-persistence/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><item><title>Integrating a Database Service (PostgreSQL)</title><link>https://ai-blog.noorshomelab.dev/docker-compose-prod-stack-2026/integrating-database-service/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-compose-prod-stack-2026/integrating-database-service/</guid><description>&lt;p&gt;Modern applications demand robust data storage. In this chapter, we&amp;rsquo;ll integrate a PostgreSQL database into our Docker Compose stack, transforming our simple web application into a dynamic system capable of storing and retrieving information persistently. By the end, you&amp;rsquo;ll have a fully containerized, multi-service application with a reliable database backend, a cornerstone for any production system.&lt;/p&gt;
&lt;h3 id="project-overview-adding-persistent-data"&gt;Project Overview: Adding Persistent Data&lt;/h3&gt;
&lt;p&gt;Our overall project aims to build a production-ready multi-service application using Docker Compose. Until now, our web application has been stateless. This chapter introduces a stateful component: a PostgreSQL database. This allows our application to manage user accounts, store content, or maintain any dynamic state required for its functionality. We will focus on ensuring the database&amp;rsquo;s data persists across container restarts and updates, a critical aspect for production environments.&lt;/p&gt;</description></item><item><title>Chapter 6: Persistent Data with Volumes</title><link>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/06-persistent-data-volumes/</link><pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/06-persistent-data-volumes/</guid><description>&lt;h2 id="chapter-6-persistent-data-with-volumes"&gt;Chapter 6: Persistent Data with Volumes&lt;/h2&gt;
&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Welcome back, intrepid container explorer! In the previous chapters, you mastered the art of running and managing ephemeral containers. You learned how to launch a simple web server, but what happens to its data when the container stops or is removed? Poof! It&amp;rsquo;s gone. This ephemeral nature is fantastic for stateless applications, but most real-world applications, like databases, logging services, or applications with user-uploaded content, need their data to stick around.&lt;/p&gt;</description></item><item><title>Chapter 8: Data Persistence: SwiftData, Core Data &amp;amp; Local Storage</title><link>https://ai-blog.noorshomelab.dev/ios-pro-dev-2026-guide/data-persistence/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ios-pro-dev-2026-guide/data-persistence/</guid><description>&lt;h2 id="chapter-8-data-persistence-swiftdata-core-data--local-storage"&gt;Chapter 8: Data Persistence: SwiftData, Core Data &amp;amp; Local Storage&lt;/h2&gt;
&lt;p&gt;Welcome back, future iOS rockstar! So far, you&amp;rsquo;ve learned how to make beautiful interfaces and manage your app&amp;rsquo;s temporary state. But what happens when your users close the app? Poof! All that hard work, all that data, gone. That&amp;rsquo;s where &lt;strong&gt;data persistence&lt;/strong&gt; comes in.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to dive deep into how your iOS apps can remember things, even after they&amp;rsquo;re closed. We&amp;rsquo;ll explore various strategies, from simple key-value storage to powerful object graph management with Apple&amp;rsquo;s modern framework, &lt;strong&gt;SwiftData&lt;/strong&gt;. By the end, you&amp;rsquo;ll understand when to use each tool and gain hands-on experience saving and loading data like a pro. Get ready to give your apps a memory!&lt;/p&gt;</description></item><item><title>Chapter 6: Docker Storage and Data Persistence</title><link>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-6-docker-storage-and-data-persistence/</link><pubDate>Sun, 23 Nov 2025 22:00:12 +0530</pubDate><guid>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-6-docker-storage-and-data-persistence/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the previous chapters, we learned how to create, run, and manage Docker containers. However, one fundamental aspect we haven&amp;rsquo;t deeply explored is how Docker handles data. By default, the data generated by a container is stored within the container&amp;rsquo;s writable layer, which is ephemeral. This means that if you remove the container, all its data is lost. This behavior is problematic for applications that need to store persistent data, such as databases, logs, or user-uploaded files.&lt;/p&gt;</description></item></channel></rss>