Traditional Registry
Section2: Container Registry Architectures
Scope of the topic for research:
- Scope Clarity: Covers all three systems (traditional, Bolt, DupHunter) under the umbrella of registry architectures.
- Progression: Highlights the evolution from basic designs to advanced optimizations (deduplication).
- Research Focus: Aligns with your goal of improving storage efficiency via block-level deduplication.
Architectural comparison
-
Traditional Registry: A centralized Docker image storage system (e.g., Docker Hub, Harbor) that uses separate components (load balancers, stateless registry servers, and backend storage like S3) to manage and serve container images.
-
Bolt: A hyper-converged Docker registry design where each node combines compute, storage, and load balancing using consistent hashing and ZooKeeper to eliminate bottlenecks and reduce latency.
-
DupHunter: A specialized Docker registry that adds block-level deduplication to reduce storage costs while optimizing layer restore performance through caching and prefetching.
Key Differences:
- Traditional: Decoupled, scalable but high-latency.
- Bolt: Unified nodes for low-latency but no deduplication.
- DupHunter: Deduplication-focused but trades off restore speed.