Design Holographic Conference - System Design | WinJob

Holographic conference problem framing and telepresence model

Enterprise holographic telepresence replaces flat video with volumetric presence: depth cameras or LiDAR rigs capture a performer, encoders shrink point clouds or mesh sequences, and remote light-field or waveguide displays reconstruct parallax. Microsoft Mesh and Cisco Webex hologram pilots prove the control plane must stay separate from the heavy media plane.

Numbers to state early

50K: 50K concurrent rooms
8: 8 speakers/stage
120ms: 120ms glass-to-glass

Failure and edge cases

Capture node dropout triggers last-keyframe hold plus audio-only fallback for 3 seconds. Encoder backlog switches to adaptive bitrate ladder dropping splat count before freezing lipsync.

Java

javaOne Dark Pro

1 public final class VolumetricFrameId {
2   private final String sessionId;
3   private final long sequence;
4   private final int codecGeneration;
5  
6   public VolumetricFrameId(String sessionId, long sequence, int codecGeneration) {
7     this.sessionId = sessionId;
8     this.sequence = sequence;
9     this.codecGeneration = codecGeneration;
10   }
11  
12   public String key() {
13     return sessionId + ":" + sequence + ":" + codecGeneration;
14   }
15 }

Python

pythonOne Dark Pro

1 @dataclass(frozen=True)
2 class VolumetricFrameId:
3     session_id: str
4     sequence: int
5     codec_generation: int
6  
7     def key(self) -> str:
8         return f"{self.session_id}:{self.sequence}:{self.codec_generation}"

TypeScript

typescriptOne Dark Pro

1 export interface VolumetricFrameId {
2   sessionId: string;
3   sequence: number;
4   codecGeneration: number;
5 }
6  
7 export function frameKey(frame: VolumetricFrameId): string {
8   return `${frame.sessionId}:${frame.sequence}:${frame.codecGeneration}`;
9 }

Why interviewers care

Holographic Conference interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Holographic conference problem framing and telepresence model that proves you understand real outages, not happy-path diagrams.

Key Highlights

•50K concurrent rooms
•Capture Rig -> Encoder -> Display
•Enterprise holographic telepresence replaces flat video with volumetric presence: depth capture rigor.

1	public final class VolumetricFrameId {
2	private final String sessionId;
3	private final long sequence;
4	private final int codecGeneration;
5
6	public VolumetricFrameId(String sessionId, long sequence, int codecGeneration) {
7	this.sessionId = sessionId;
8	this.sequence = sequence;
9	this.codecGeneration = codecGeneration;
10	}
11
12	public String key() {
13	return sessionId + ":" + sequence + ":" + codecGeneration;
14	}
15	}

1	@dataclass(frozen=True)
2	class VolumetricFrameId:
3	session_id: str
4	sequence: int
5	codec_generation: int
6
7	def key(self) -> str:
8	return f"{self.session_id}:{self.sequence}:{self.codec_generation}"

1	export interface VolumetricFrameId {
2	sessionId: string;
3	sequence: number;
4	codecGeneration: number;
5	}
6
7	export function frameKey(frame: VolumetricFrameId): string {
8	return `${frame.sessionId}:${frame.sequence}:${frame.codecGeneration}`;
9	}