Design production-ready dedup service
AnthropicSoftware Engineer · Technical ScreenLast updated
This question evaluates system design and distributed storage competencies, focusing on scalable file deduplication, content-defined chunking, metadata and index design, multi-tenant architectures, and operational reliability across regions.
Design a production-ready file deduplication service. Outline the architecture (ingest, chunking, indexing, storage, and metadata), APIs, and read/write workflows. Explain strategies for consistency, idempotency, fault isolation, failure recovery, and disaster recovery; how to run backfills and compaction/garbage collection safely; index sharding and rebalancing; deployment, rollout/rollback, and schema/version migration plans. Define monitoring, alerting, and SLOs; capacity planning and cost controls (compute, storage, network); privacy and compliance considerations (e.g., encryption, access control, GDPR); and techniques to minimize impact on production workloads (e.g., rate limiting, backpressure, priority queues).
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.