/v1.5/docs/5_architecture_and_components/package-cache/functionality/Recent content in Cache Functionality on Porch DocumentationHugoen-us/v1.5/docs/5_architecture_and_components/package-cache/functionality/repository-synchronization/Mon, 01 Jan 0001 00:00:00 +0000/v1.5/docs/5_architecture_and_components/package-cache/functionality/repository-synchronization/<h2 id="overview">Overview</h2><p>The Package Cache synchronization system manages the synchronization of package repositories between external Git sources and the internal cache. Both cache implementations (CR Cache and DB Cache) utilize a common SyncManager to handle periodic and one-time synchronization operations.</p> <h3 id="high-level-architecture">High-Level Architecture</h3><p><img src="/v1.5/images/porch/repository-sync.svg" alt="Repository Sync Architecture" /></p> <a href="/v1.5/images/porch/repository-sync-interactive.html" target="_blank">📊 Interactive Architecture Diagram</a> <h2 id="core-components">Core Components</h2><h3 id="1-syncmanager">1. SyncManager</h3><p><strong>Purpose</strong>: Central orchestrator for repository synchronization operations.</p> <p><strong>Components</strong>:</p> <ul> <li><strong>Handler</strong>: Interface for cache-specific sync operations</li> <li><strong>Core Client</strong>: Kubernetes API client for cluster communication</li> <li><strong>Next Sync Time</strong>: Tracks when the next synchronization should occur</li> <li><strong>Last Sync Error</strong>: Records any errors from previous sync attempts</li> </ul> <p><strong>Goroutines</strong>:</p>/v1.5/docs/5_architecture_and_components/package-cache/functionality/caching-behavior/Mon, 01 Jan 0001 00:00:00 +0000/v1.5/docs/5_architecture_and_components/package-cache/functionality/caching-behavior/<h2 id="overview">Overview</h2><p>The Package Cache optimizes performance by storing repository data in memory (CR Cache) or database (DB Cache) to avoid redundant Git operations. The caching system uses lazy loading, version-based refresh, and concurrency control to balance performance with data freshness.</p> <h3 id="high-level-architecture">High-Level Architecture</h3><pre tabindex="0"><code>┌─────────────────────────────────────────────────────────┐ │ Caching System │ │ │ │ ┌──────────────┐ ┌──────────────┐ ┌──────┐ │ │ │ Cache │ │ Version │ │ Git │ │ │ │ Population │ ───&gt; │ Tracking │ ───&gt; │ Repo │ │ │ │ │ │ │ │ │ │ │ │ • Lazy Load │ │ • Compare │ │ │ │ │ │ • Refresh │ │ • Refresh │ │ │ │ │ └──────────────┘ └──────────────┘ └──────┘ │ │ │ │ │ │ └──────────┬───────────┘ │ │ ↓ │ │ ┌──────────────────┐ │ │ │ Cache Structure │ │ │ │ │ │ │ │ • Maps │ │ │ │ • Mutex │ │ │ │ • Consistency │ │ │ └──────────────────┘ │ └─────────────────────────────────────────────────────────┘ </code></pre><h2 id="cache-population">Cache Population</h2><p>The cache uses lazy loading and version-based refresh to minimize Git operations:</p>