Patch delivery
Four million players. One hour. One patch.
Content-defined chunking turns a 62 GB build update into a 3.1 GB download, peer assistance takes two-thirds of that off your CDN bill, and the launcher SDK handles the rest.
The four hard parts
Content-defined chunking
Assets are chunked on content boundaries, not fixed offsets, so inserting four bytes into a package file does not invalidate everything after it. This is the difference between a 3 GB patch and a 62 GB re-download.
Peer assistance that behaves
Players fetch chunks from each other with strict upload caps, NAT traversal that actually works, and an opt-out that is honoured. Two-thirds of release-day bytes never touch our CDN.
Integrity end to end
Every chunk is hashed, every manifest is signed, and the launcher verifies before it writes. A corrupted peer cannot produce a corrupted install.
Resume, always
Interrupted at 94%? It resumes at 94%, across reboots, network changes and a laptop lid. The verification pass is incremental rather than a full rehash.