Design a Docker artifact system for cost, traceability, and speed
Tests cost-speed-auditability tradeoffs for artifacts at scale. Strong answers cover tiered storage with lifecycle policies,immutable build provenance,regional caching, and automated garbage collection. Red flag: infinite mutable storage with no cleanup rules.
Tests balancing cost, speed, and auditability across many pipelines and teams. A strong answer covers four layers: tiered storage with lifecycle policies that archive or delete stale images; immutable tags and provenance metadata linking digests to git commits and CI runs; regional pull-through caches or local mirrors to avoid cross-continent pulls; and automated garbage collection with team quotas and retention rules for dev versus prod releases.
Read the original → cloud.google.com
- #ci/cd
- #devops
- #artifact management
- #docker
- #cost optimization
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.