.git Issue #1432

📋 Problem Statement

Current deployment pipelines bundle dependencies on every cold start, adding 1.2s–2.8s to initial boot time for Node.js/Python runtimes. This impacts serverless functions and preview environments significantly.

We need a distributed pre-bundling layer that caches optimized dependency bundles at the edge, reducing cold starts to <200ms while maintaining deterministic builds.

🔧 Proposed Solution

Introduce git edge bundle CLI command to generate versioned lockfiles
Cache bundles in regional edge nodes using content-addressable storage (CAS)
Fallback to local bundling if edge cache misses or integrity fails
Expose cache hit/miss metrics in deployment logs

                                edge-config.yaml
                                v2.1.0
                            

build:
  edge_cache: true
  runtime: nodejs20.x
  regions: [us-east-1, eu-west-2, ap-south-1]
  ttl: 24h
  
# Fallback strategy
fallback:
  strategy: local-build
  timeout: 30s
                            

🕒 Activity Timeline

@dev-lead • 2 hours ago

Changed status to In Progress. Starting RFC draft for cache invalidation strategy.

@sysarch • Yesterday at 14:32

Added enhancement label. This aligns with Q3 performance goals.

@cli-team • 3 days ago

Initial POC benchmark: 1.8s → 0.14s cold start improvement on eu-west region.

@issue-bot • 5 days ago

Issue created. Assigned to @platform-team. Milestone: v3.2.0

💬 Comments (3)

MR

Marcus Rivera 1 day ago

We should consider cache warming on `git deploy --preview`. Also, what's the eTag strategy when `package.json` changes but `node_modules` content hash remains identical?

SK

Sarah Kim 18 hours ago

Good catch. We'll use composite hashing: `.`. If either changes, cache invalidates. I'll update the spec doc.

AL

Aisha Liang 6 hours ago

Security team approved the CAS design. Ready for implementation sprint starting Monday. Linking internal RFC: docs.git.internal/rfc/1432-cache