Caching Proxy Configuration on the Traffic Control CDN
summary
A Perl monolithic cache-config tool is rewritten in Go as a set of POSIX-style apps that actually run: t3c apply, t3c request | t3c generate, t3c check/diff/pre-process/update, each handling one step of pulling Traffic Ops JSON, generating ATS files, diffing (ignoring comment-only changes) and unsetting update flags. The pipeline runs in ~20 seconds versus 15–20 minutes before, uses git backups for config history, ships man pages and standard filesystem locations, and is live in the Apache Traffic Control codebase.
AI-written summary · about
chapters (8)
- 0:00Introduction to T3C
- 1:37From ORT to T3C
- 5:05Goals and design principles
- 6:58T3C sub-command breakdown
- 10:11Installation and operation
- 17:24Demonstrating composability
- 24:35Removal of dispersion
- 28:36Q&A and future outlook
related talks
33mTaming the Beast: Understanding and Harnessing the Power of HTTP Proxies
23mCacheCatalyst: Enhancing Web Caching for the Latency-Constrained Internet
39mHTTP Caching for REST APIs
26mWhat’s next in the HTTP caching world
30mCacheFilter: Flexible HTTP Caching in Envoy
24mAre We Turbo Yet?
58mCaching the uncacheable: delivering personalized experiences without sacrificing performance
41mCaching Like a Pro: Best strategies for dealing with Drupal cache