<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Persistence on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/persistence/</link><description>Recent content in Persistence on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/persistence/index.xml" rel="self" type="application/rss+xml"/><item><title>Implementing Persistent Agent State with External Storage</title><link>https://ai-blog.noorshomelab.dev/adk-persistent-agents-2026/implementing-persistent-state/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/adk-persistent-agents-2026/implementing-persistent-state/</guid><description>&lt;p&gt;In the previous chapter, we established a basic AI agent and managed its conversational context in memory. While useful for short, single-session interactions, this approach falls short for long-running agents that need to survive restarts, process background tasks, or maintain context across multiple user sessions. Losing an agent&amp;rsquo;s state means losing its memory, its progress, and ultimately, its utility. Without persistence, a crash or planned shutdown erases all prior interactions, forcing the agent to start anew, which is unacceptable for production systems.&lt;/p&gt;</description></item><item><title>Storing Agent Memories: From Files to Databases and Vector Stores</title><link>https://ai-blog.noorshomelab.dev/ai-agent-memory-2026/storing-agent-memories/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-agent-memory-2026/storing-agent-memories/</guid><description>&lt;h2 id="introduction-where-do-memories-live"&gt;Introduction: Where Do Memories Live?&lt;/h2&gt;
&lt;p&gt;Welcome back, aspiring agent architects! In our previous chapters, we dove deep into the fascinating world of AI agent memory, exploring different types like working, short-term, long-term, episodic, and semantic memory. We understood &lt;em&gt;what&lt;/em&gt; these memories are and &lt;em&gt;why&lt;/em&gt; an agent needs them to be intelligent, adaptive, and capable of complex interactions.&lt;/p&gt;
&lt;p&gt;But here&amp;rsquo;s a crucial question: where do these memories actually &lt;em&gt;live&lt;/em&gt;? How do we take an agent&amp;rsquo;s insights, past conversations, learned facts, or specific experiences and store them so they can be retrieved later? Just like humans rely on different parts of their brain for different types of recall, AI agents need various storage mechanisms to keep their memories safe and accessible.&lt;/p&gt;</description></item><item><title>Data That Stays - Introduction to Docker Volumes</title><link>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-05-docker-volumes/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-05-docker-volumes/</guid><description>&lt;h2 id="data-that-stays---introduction-to-docker-volumes"&gt;Data That Stays - Introduction to Docker Volumes&lt;/h2&gt;
&lt;p&gt;Welcome back, aspiring Docker master! So far, we&amp;rsquo;ve learned how to create, run, and manage containers. You&amp;rsquo;ve seen how powerful they are for packaging applications. But there&amp;rsquo;s a tiny &amp;ldquo;gotcha&amp;rdquo; we need to address: what happens to your data when a container stops or gets removed? Poof! It&amp;rsquo;s gone. That&amp;rsquo;s not ideal for most real-world applications, right?&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to tackle this challenge head-on by introducing &lt;strong&gt;Docker Volumes&lt;/strong&gt;. You&amp;rsquo;ll discover how to make your containerized applications store data persistently, ensuring your important information survives even if your containers don&amp;rsquo;t. This is a fundamental concept for building robust, production-ready Docker applications, so get ready to make your data truly &lt;em&gt;stay&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Chapter 9: Designing the Data Model &amp;amp; Persistence with JPA/Hibernate</title><link>https://ai-blog.noorshomelab.dev/java-mini-projects/ch09-data-model-jpa/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mini-projects/ch09-data-model-jpa/</guid><description>&lt;h2 id="chapter-9-designing-the-data-model--persistence-with-jpahibernate"&gt;Chapter 9: Designing the Data Model &amp;amp; Persistence with JPA/Hibernate&lt;/h2&gt;
&lt;h3 id="chapter-introduction"&gt;Chapter Introduction&lt;/h3&gt;
&lt;p&gt;Welcome to Chapter 9! In this chapter, we&amp;rsquo;re taking a significant leap in building our &amp;ldquo;Basic To-Do List Application&amp;rdquo; by introducing data persistence. Up until now, any data we&amp;rsquo;ve worked with would vanish as soon as our application stopped. That&amp;rsquo;s not very useful for a To-Do list! Here, we will design the data model for our To-Do items and implement the persistence layer using Java Persistence API (JPA) with Hibernate, backed by Spring Data JPA.&lt;/p&gt;</description></item><item><title>Intermediate Topics: Persistence and Data Durability</title><link>https://ai-blog.noorshomelab.dev/redis-guide/persistence-and-durability/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/redis-guide/persistence-and-durability/</guid><description>&lt;p&gt;Redis is primarily an in-memory data store, which gives it its incredible speed. However, memory is volatile; if the Redis server crashes or is shut down, all data in memory would be lost. To prevent this, Redis offers &lt;strong&gt;persistence mechanisms&lt;/strong&gt; that allow you to save your dataset to disk. This chapter will delve into the two main persistence options: &lt;strong&gt;RDB (Redis Database Backup)&lt;/strong&gt; and &lt;strong&gt;AOF (Append-Only File)&lt;/strong&gt;, and discuss best practices for data durability.&lt;/p&gt;</description></item><item><title>Project 2: Offline-First Task Manager</title><link>https://ai-blog.noorshomelab.dev/ios-pro-dev-2026-guide/project-offline-task-manager/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ios-pro-dev-2026-guide/project-offline-task-manager/</guid><description>&lt;h2 id="project-2-offline-first-task-manager"&gt;Project 2: Offline-First Task Manager&lt;/h2&gt;
&lt;p&gt;Welcome back, future iOS professionals! In our previous project, you built a foundational social app, touching on core UI and navigation. Now, we&amp;rsquo;re diving into a crucial aspect of modern app development: &lt;strong&gt;offline-first design&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll embark on building an &amp;ldquo;Offline-First Task Manager&amp;rdquo; application. This project will teach you how to create an app that remains fully functional and responsive even when the user has no internet connection. We&amp;rsquo;ll leverage Apple&amp;rsquo;s modern frameworks, SwiftUI for the user interface and SwiftData for robust local data persistence, alongside the Network framework for connectivity monitoring.&lt;/p&gt;</description></item><item><title>Building Persistent AI Agents with Google ADK: Pause, Resume, Recover</title><link>https://ai-blog.noorshomelab.dev/projects/google-adk-persistent-agents-guide/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/projects/google-adk-persistent-agents-guide/</guid><description>&lt;h2 id="building-persistent-ai-agents-with-google-adk-pause-resume-recover"&gt;Building Persistent AI Agents with Google ADK: Pause, Resume, Recover&lt;/h2&gt;
&lt;p&gt;Imagine an AI agent assisting a customer, gathering information, and then needing to pause its work—perhaps the customer needs to find a document, or the agent needs to wait for an external system. If that agent loses all memory of the conversation and its current task when it pauses, it&amp;rsquo;s not truly helpful. This guide addresses that critical challenge: building AI agents that can maintain context and state across sessions, allowing for seamless pause, resume, and recovery from interruptions without losing valuable information.&lt;/p&gt;</description></item><item><title>Interacting with Files: Reading and Writing Data</title><link>https://ai-blog.noorshomelab.dev/python-mastery-2025/chapter-9-interacting-with-files-reading-writing-data/</link><pubDate>Wed, 03 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/python-mastery-2025/chapter-9-interacting-with-files-reading-writing-data/</guid><description>&lt;h2 id="chapter-9-interacting-with-files-reading-and-writing-data"&gt;Chapter 9: Interacting with Files: Reading and Writing Data&lt;/h2&gt;
&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Welcome back, Python adventurer! So far, we&amp;rsquo;ve learned how to store data in variables, organize it in lists and dictionaries, and process it with loops and functions. But what happens to our data when our program finishes running? Poof! It&amp;rsquo;s gone. That&amp;rsquo;s where file interaction comes in!&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to unlock the power of &lt;strong&gt;file I/O&lt;/strong&gt; (Input/Output). You&amp;rsquo;ll learn how to create new text files, write information into them, read existing data from them, and even add new content without erasing the old. This ability to persist data is a cornerstone of almost every useful application, from saving game progress to logging important events, or even storing user preferences. Get ready to make your Python programs remember things!&lt;/p&gt;</description></item></channel></rss>