# System-design interview question: peer-to-peer file distribution

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/questions/5781/design-p2p-file-distribution-system
Source observed: 2026-11-04T23:34:30.456Z
Last checked: 2026-11-04T23:34:30.456+00:00
Indexed: 2026-11-05T13:01:11.762+00:00

---

# Design a peer-to-peer file distribution system

We provide this system-design interview question:

> Design a peer-to-peer file distribution system that spreads a 10GB file from a single bandwidth-constrained source to thousands of interconnected hosts, each with limited input/output bandwidth, until every machine has the file.

The prompt asks candidates to reason about distributing a large file through a network in which the original source and every host have bandwidth limits.

## Question details

- **Reported category:** [System Design](https://www.aced.io/questions?type=system-design)
- **Reported roles:** [Hardware Engineer](https://www.aced.io/questions?role=hardware-engineer), [Software Engineer](https://www.aced.io/questions?role=swe)
- **Reported company:** [Anthropic](https://www.aced.io/questions?company=anthropic) (2)
- **Interview count shown:** 2 interviews
- **Last asked:** a year ago
- **Saved by:** 7 users

Detailed company statistics are available through [Upgrade](https://www.aced.io/upgrade?src=questions).

## Key trade-off

The prompt highlights the trade-off between distributing the file one host at a time and splitting the available bandwidth across multiple hosts.

## Community answers

No answers have been contributed by the community yet.

## Related question

- [Design an inference batching system for a single GPU that can handle up to 100 inputs per batch while users wait synchronously, maximizing utilization under compute constraints.](https://www.aced.io/questions/5780/inference-batching-system)

## Related courses

### [Software Engineering Interview Prep](https://www.aced.io/courses/software-engineering)

We prepare candidates for software-engineering roles at Google, Amazon, Microsoft, Meta, Apple, and other companies through mock interviews, frameworks, and advice from senior candidates. The course covers data structures, algorithms, system design, people management, behavioral interviews, and more.

![Software Engineering Interview Prep](https://images.ctfassets.net/x78yjrjc11pq/4VkuYewBHUFIVUS5oJDW5h/02e833439b1289f25f38f13f81cbdca3/adobe_stock_optimized.jpeg?w=800&h=800&fm=webp&q=75)

### [System Design Interviews](https://www.aced.io/courses/system-design-interviews)

We teach how to answer current system-design questions across product, infrastructure, and AI domains, with in-depth video examples, written breakdowns, reference patterns, and mock-interview answers from senior engineers and managers.

![System Design Interviews](https://images.ctfassets.net/x78yjrjc11pq/78x7miFZFjBCrM5GqftrMJ/2f6d26e632c4e7265c49f6a180227edb/system_design_track_compressed_26ac98a46e__281_29_5be2280f31.jpeg?w=800&h=800&fm=webp&q=75)

## Submit an answer

Submitting an answer marks the question complete.

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F5781%2Fdesign-p2p-file-distribution-system&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F5781%2Fdesign-p2p-file-distribution-system). Opening a form does not execute a tool.