Modernizing Artifact Storage at Uber

What this post added

This post details the migration from a legacy on-premise artifact storage system to a cloud-native SaaS offering, coupled with the introduction of a purpose-built validation proxy layer. The proxy layer addresses the challenge of high egress costs from the SaaS platform by implementing conditional requests (If-None-Match, If-Modified-Since) and maintaining an artifact metadata store (MySQL) to validate content against the authoritative source. This approach reduces data egress by over 99% and ensures correctness through per-request validation rather than time-based cache expiration. The architecture is deployed across two Uber data centers, pinned to nearest cloud regions for active-active operation and failover.