Practice/Meta/Design a system that will handle cloud saves from an Oculus VR headset

Design a system that will handle cloud saves from an Oculus VR headset

Product DesignOptional

Problem Statement

You need to architect a cloud-based save system for a VR gaming platform that automatically backs up user progress, game states, and configuration settings from standalone VR headsets. Players should be able to seamlessly continue their gaming experience when switching between different headsets, after device replacements, or when reinstalling games. The system must handle millions of active users playing hundreds of different VR titles, with save files ranging from small configuration files (kilobytes) to large world states (hundreds of megabytes).

The solution needs to balance sync frequency with battery life constraints on wireless VR devices, handle offline gameplay gracefully, and resolve conflicts when users play the same game on multiple devices. You should consider the unique challenges of VR gaming, including motion sickness if sync delays cause progress loss, and the resource constraints of mobile VR processors.

Key Requirements

Functional

• Automatic Save Sync -- detect and upload save file changes without requiring user intervention
• Cross-Device Restoration -- allow users to download and restore saves on any authorized headset
• Conflict Resolution -- handle scenarios where the same game is played offline on multiple devices
• Per-Game Storage -- manage separate save states for each installed game with proper isolation
• Version Control -- maintain save history to allow users to recover from corrupted or unwanted saves

Non-Functional

• Scalability -- support 10M+ active users with 50M+ daily save operations across 1000+ games
• Reliability -- ensure 99.9% availability with no data loss even during partial system failures
• Latency -- complete background uploads within 30 seconds; restore operations within 5 seconds
• Consistency -- provide eventual consistency with strong consistency for conflict resolution
• Efficiency -- minimize battery drain on wireless headsets through intelligent batching and compression

What Interviewers Focus On

Based on real interview experiences, these are the areas interviewers probe most deeply:

1. Client-Side Sync Strategy

Understanding how to detect save file changes on resource-constrained VR hardware without draining battery or impacting game performance is critical.

Hints to consider:

• File system watchers vs. periodic scanning vs. game SDK hooks for change detection
• Delta sync vs. full file upload strategies to minimize bandwidth usage
• Background task scheduling that respects VR headset thermal and battery constraints
• Handling the transition between online and offline modes seamlessly

2. Conflict Resolution Architecture

When users play the same game offline on multiple headsets, conflicting save states emerge that must be resolved intelligently.

Hints to consider:

• Using vector clocks or logical timestamps to track save causality across devices
• Defining merge strategies: last-write-wins, custom per-game logic, or user choice
• Designing an API that allows game developers to implement custom conflict resolution
• Storing metadata like playtime, device ID, and session timestamps to inform resolution

3. Storage Architecture and Data Modeling

Organizing save data for billions of files across millions of users and thousands of games requires careful schema design.

Hints to consider:

• Partitioning strategy (by user, by game, or hybrid) for distributed storage
• Using object storage (S3-like) vs. database blobs vs. specialized file systems
• Metadata indexing for quick lookups: user → games → save versions
• Implementing retention policies and automatic cleanup of old save versions

4. Network Efficiency and Bandwidth Optimization

VR headsets often operate on WiFi with varying quality, making efficient data transfer crucial.

Hints to consider:

• Content-defined chunking for deduplication of similar save files
• Compression algorithms optimized for game save file formats
• Resume capability for interrupted uploads/downloads
• Adaptive sync strategies based on network conditions and device state

Suggested Approach

Step 1: Clarify Requirements

Start by confirming the scope and constraints with your interviewer. Ask about the number of concurrent users, typical save file sizes across different game types (puzzle games vs. open-world RPGs), how frequently saves occur during gameplay, expected device count per user, and whether the system needs to support legacy games or only new titles with SDK integration. Clarify whether you need to design the client component, backend services, or both.