Design Mind Mapping Tool - System Design | WinJob

Problem framing: hierarchical mind maps at collaboration scale

A mind-mapping tool is a directed graph editor where users create topic nodes, parent-child edges, and optional cross-links while panning an infinite canvas. Unlike Kanban boards, the primary invariant is acyclic tree semantics per root with controlled exceptions for reference links. Interviewers expect you to separate structural graph mutations (add node, reparent, relabel) from layout hints (auto-arrange radial vs. organic) and ephemeral presence (cursor, selection halo, follow mode).

Miro and MindMeister production patterns: operation log per map_id with monotonic sequence, snapshot compaction when node count exceeds ~8k, and WebSocket fanout scoped to map room. Assume 22M MAU, 95M maps, median map 420 nodes / 1.1 MB serialized, 8 concurrent editors on workshop maps, 180 structural ops/s on hot maps during brainstorms.

Java

javaOne Dark Pro

1 public final class MapShardKey {
2   public String route(String orgId, String mapId) {
3     if (orgId == null || mapId == null) throw new IllegalArgumentException("required");
4     return orgId + ":" + mapId;
5   }
6 }

Python

pythonOne Dark Pro

1 def map_shard_key(org_id: str, map_id: str) -> str:
2     if not org_id or not map_id:
3         raise ValueError("required")
4     return f"{org_id}:{map_id}"

TypeScript

typescriptOne Dark Pro

1 export function mapShardKey(orgId: string, mapId: string): string {
2   if (!orgId || !mapId) throw new Error("required");
3   return `${orgId}:${mapId}`;
4 }

Deep dive (Problem framing: hierarchical mind maps at collaboration scale)

Interviewers at Miro/MindMeister often probe partial subtree moves during live workshops: you must explain how MOVE_NODE preserves sibling ordering with after_sibling_id and why concurrent moves to the same parent serialize through the map leader rather than last-write-wins timestamps. When users attach screenshots to nodes, presigned PUT keeps bytes off Kafka; only ATTACH_READY events enter the op log so virus scanning cannot block unrelated edits.

For enterprise tenants, reference legal hold on compaction and share-link audit streams—signals you have shipped collaboration products, not only read CRDT blogs. Quantify again: 22M MAU, 180 ops/s hot map, 60ms structural p95, 1.1 MB median hydrate. If asked about AI topic expansion, park it behind async workers consuming NODE_LABEL_CHANGED so GPU spend never shares the sync leader CPU pool.

Failure drill

Leader dies mid-brainstorm: Redis lease expires, standby promotes, Kafka tail replays from committed offset, clients receive RESYNC with snapshot URL—no manual refresh if last_ack_seq within 50k window. If lag beyond 50k, SNAPSHOT_REQUIRED forces full hydrate—state this aloud in interviews.

Section 1 checklist

Cite one numeric assumption tied to mind maps (not generic traffic).
Name one service boundary you own (Map Service vs. Sync Gateway vs. Export Worker).
Call out one trade-off you rejected (full map CRDT, row-per-node SQL, P2P sync).

Why interviewers care

Mind Mapping Tool interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Problem framing: hierarchical mind maps at collaboration scale that proves you understand real outages, not happy-path diagrams.

Key Highlights

•Graph mutations differ from layout and presence
•Hot maps hit ~180 structural ops/s
•Snapshots compact beyond ~8k nodes

1	public final class MapShardKey {
2	public String route(String orgId, String mapId) {
3	if (orgId == null \|\| mapId == null) throw new IllegalArgumentException("required");
4	return orgId + ":" + mapId;
5	}
6	}

1	def map_shard_key(org_id: str, map_id: str) -> str:
2	if not org_id or not map_id:
3	raise ValueError("required")
4	return f"{org_id}:{map_id}"

1	export function mapShardKey(orgId: string, mapId: string): string {
2	if (!orgId \|\| !mapId) throw new Error("required");
3	return `${orgId}:${mapId}`;
4	}