Prompt
Should I move app files off local disks before scaling?
Latest observation
Oct 12, 2026
OpenAI APIWeb search: off
Usually yes—if you plan to scale beyond a single machine, move app files off local disks before scaling, but it depends on what the files are used for.
Move them off local disk if they are:
- User uploads
- Shared media/assets
- Generated files that must survive restarts
- Anything that needs to be visible to multiple app instances
Use shared storage such as:
- Object storage: S3, GCS, Azure Blob
- Shared network storage: NFS, EFS, Filestore, etc.
Keep them local if they are:
- Ephemeral caches
- Temporary build artifacts
- Per-instance scratch space
- Data that can be regenerated
Why this matters for scaling
If you add more app instances and each one has its own local disk:
- Users may hit different instances and not see the same files
- A pod/container restart can delete files
- Load balancing can cause inconsistent behavior
- Horizontal scaling becomes unreliable
Good rule of thumb
If the file is part of your app’s state, don’t keep it only on local disk unless you’re intentionally using a single-instance setup.
Practical migration approach
- Identify which files are persistent vs temporary
- Move persistent files to shared storage
- Update app code to read/write from the shared location
- Test with multiple app instances
- Then scale out
If you want, I can help you classify your app files into:
- safe to keep local,
- should move to object storage,
- should move to shared filesystem.